It may not be simply a disk space/parser issue.
In our case it's a banswith issue. When you are dealing with hundreds upon hundreds of transactions per second, size does matter!
In our case, we are looking into compressing the stream to handle these issues.
No, xerces won't parse your example...
-Pete
| Tom Bradford <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 05/23/2001 02:24 PM
|
To: [EMAIL PROTECTED] cc: Subject: Re: Terminating with </> |
James Richardson wrote:
> I've been asked to integrate some java with a c++ program that spits out (almost) xml. The xml looks something like this
>
> <Request>
> <Service Act="Subscribe" Dest=":Naming:">
> <ServiceAttr>SomeValue</>
> </Service>
> </Request>
>
> That is, the terminating tag can be _either_ </> or </name>. I know that this is not true xml, but it can make for significantly shorter messages.
>
> Is this something that I can parse out-of-the-box with xerces-j?
If it were, I'd be very surprised and disappointed. Disk space is
cheap, and parsers are free, so it's probably far more economical to ask
the c++ programmers to actually spit out proper XML than this
bastardization of it. It will only help them in the end.
--
Tom Bradford --- The dbXML Project --- http://www.dbxml.org/
We store your XML data a hell of a lot better than /dev/null
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
