Hi Sven From: "Sven Behrens" <[EMAIL PROTECTED]> > Hi James, > > > BTW the best way to transmit XML documents across serialization is actually > > just to use text rather than Java Serialization. > > OK, I knew that, but since I never really had trouble using the default, > I wonder what to gain by using text-transmission.
Performance. > And how would I have to do that: I have some classes with (among others) > a dom4j-Document-member. Are there any examples arround on how to modify > standard-serialization on these classes to convert the document to a > String before serialization (and the other way round)? Or what is the > way you recommend to do this? And why doesn't dom4j use this kind of > serialization internally? I nearly made Document use text internally by default. I think its a good idea since serializing DOM-ish structures using Java Serializaiton is a bit silly really. Dennis Sosnoski did some cool work on a more efficient binary representation thats about 30% quicker than text which I've always meant to plugin if its there on the classpath, otherwise just use text for a Document. http://www.sosnoski.com/opensrc/xmls/index.html e.g. take a look at the performace differences... http://www.sosnoski.com/opensrc/xmls/results.html If anyone fancies having a go at doing this I'd be most grateful; I'm in the process of moving dom4j over to use a Maven build at the moment to make a much nicer website. Otherwise I'll get around to doing this eventually. James _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ dom4j-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dom4j-user
