Lists Home |
Date Index |
On Thursday 25 September 2003 11:03, Sean McGrath wrote:
> In the system, each XML File Loader/Saver is responsible for
> maintaining a native object serialisation for
> each XML instance (in my case, Python/Jython pickles).
> At load time, the marshalled object is read *if* the XML has
> not changed. If the XML has changed, it is loaded and a new
> marshalled object is created. At save time, the marshalled
> object is created first, then the plain text XML.
> It works a treat and is fast enough to work within the tight
> confines of a HTTP request/response pair thread on a heavily
> loaded portal.
That sounds like a pretty neat solution to your problem. I work
in a different context where incoming documents are completely
independent so we can't maintain state on the server to assist
loading. In this case the full parse cost has to be taken for
each document at TPS up to the 10k kind of range. Binary infoset
(with optional compression) would be a clear win for us.
> The benefits of that binary thing in the middle being
> platform/product/application neutral are overstated in my
We already employ a binary encoding internally within a single
server but without a standard we can't extend the advantage we
get from the binary encoding into a bigger environment.