Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by jjohn (22) on 2003.01.15 19:19 (#16057) Homepage Journal
    I understand that you're trying to work around the large XML message problem. I take it you're not worried about validating this bloody message, rather you want to get at the data? Perhaps you'd consider just sending a pointer to the data which can then be served over standard HTTP. I think this solution keeps the XML message managable and lets RPC::XML do what it does best: small messages. I realize this is a somewhat unsettling suggestion, but I smells like the right solution to me. If you go down the road of reading the XML stream, it's not long before you start to think "Why read the rest of the XML message when I've finished reading the content I want?". Then XML becomes a hinderance, or at least an vestigal organ which future programmers will mock.

    This problem is an interesting one. I'll be interested in how you implement your solution.

    • The problem is that the 3rd-party system we're working with uses an XML-RPC interface, but the data being sent is going to be huge. The goal is to avoid constructing the XML-RPC messages as in-memory strings, since they will be including base64 values that are encoded audio attachments.

      The fact that I prefer not to back down on my existing compression support makes it harder, but I'm not going to back out a generally-useful feature like that in the name of a specific-requirement feature.

      Matts [perl.org] made a good

      --

      --rjray