powered by Jive Software

Application specific child element in error child element of IQ packets

When an error child element in a received IQ packet is parsed, only its text content is extracted. Any optional child element that would indicate an application specific error condition is skipped.

I am wondering if there is a reason why it would not make sense to have an extension mechanism to parse such error condition elements so that an application that wants to know about them can.

I could not see a thread on this subject in the discussion list but I would like to know if it has been considered in the past.

Thanks,

MB