>>> First, XML-RPC is not the only mechanism using XML over a network >>> connection. Second, you don't want to do this if you're dealing >>> with several 100 MB of data just because you want to figure >>> out the encoding. >> That's my original claim/question: what SPECIFIC application do >> you have in mind that transfers XML over a network and where you >> would want to have such a stream codec? > > XML-based web services used for business integration, e.g. based > on ebXML. > > A common use case from our everyday consulting business is e.g. > passing market and trading data to portfolio pricing web services.
I still don't see the need for this feature from this example. First, in ebXML messaging, the message are typically *not* large (i.e. much smaller than 100 MB). Furthermore, the typical processing of such a message would be to pass it directly to the XML parser, no need for the functionality under discussion. >> Right. However, I' will remain opposed to adding this to the >> standard library until I see why one would absolutely need to >> have that. Not every piece of code that is useful in some >> application should be added to the standard library. > > Agreed, but the application space of web services is large > enough to warrant this. If that was the case, wouldn't the existing Python web service libraries already include such a functionality? Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
