Hello Reinhard,

We currently have a compression mechanism in place that allows third party 
users to turn compression on, including various levels of compression + 
strategies etc... The problem we are finding to be specific is that the process 
of converting numbers (especially floats) into strings (and vice-versa) is 
extremely expensive. This is a known issue with Java, but as a lot of the work 
that our clients do involves the tranmission of numerical data, this results in 
a lot of "lost time". I guess my question was aimed at a level further up from 
the solution of embedding BinHex64 binary data into an XML file. Instead of 
inserting just floats etc.. as BinHex64, why not the whole structure.

I haven't looked into it, but I also wonder if a DOM object created in XERCES-J 
would be compatible with a XERCES DOM object for XERCES C/C++?

Thanks for the input


Rod

-----Original Message-----
From: Reinhard Brandst�dter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 7 January 2004 1:39 AM
To: [EMAIL PROTECTED]
Subject: Re: Internal Xerces structure available?


Farmer, Rod (Contractor) wrote:
> Hello, wondering if anyone else has thought about a similar problem as the 
> one below,
> 
> 
> I currently use Xerces-J to serialize Java objects to XML, send this across a 
> socket and have the corresponding object recreated in both a Java and C++. We 
> are finding that in profiling our software, significant improvements could be 
> made by removing the conversion of the internal binary XML structure to plain 
> text and sending this over the network instead. For example. determing that 
> the value of a class attribute is (int) 5, writing this as a String and 
> outputting to either a socket or file as part of a larger XML document being 
> written out.
> 
> In other words, is there some internal Xerces binary structure that we could 
> use to send data across the network instead of using a plain text XML 
> representation of the serialized Java object?

Is the problem the time it takes to convert the internal DOM to an XML 
file or the time it takes to send the XML text data over the network?

For the latter one I would try to compress the data, which should be 
quite effective since it's only text.

Reinhard

-- 
Reinhard Brandstaedter   [EMAIL PROTECTED]  GPG: 0x033B81DB
-    Student of Computer Science - J.K. University of Linz     -
-        <ICQ: 73059068>    <Mobile: +43 699 12419541>         -
-                  http://adelaide.dnsalias.net                -

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to