logo       

Related Msgs: audio.musicbrai...    enbd.general/20...    ietf.idr/2002-0...    java.ant-contri...    gnu.make.genera...    qplus.devel/200...    video.freevo.cv...    os.netbsd.ports...    yellowdog.gener...    xfree86.cvs/200...    search.nutch.us...    freedesktop.xse...    programming.swi...    capabilities.ge...    telephony.pbx.a...    mail.sylpheed.c...    db.firebase.por...    boot-loaders.u-...    recreation.radi...    netbsd.bugs/200...    web.zope.plone....    user-groups.lin...   

Re: still unsolved: parsing multiple XML from socket: msg#00011

Subject: Re: still unsolved: parsing multiple XML from socket
Peter Hendry wrote:
>
>
> Aleksander Slominski wrote:
>> Peter Hendry wrote:
>>   
>>> More efficient still would be to keep track of the last '<' and
>>> whether it had a '/' after it - then allow returning past '>' if the
>>> last '<' didn't have a '/' (confused? :-) ).
>>>     
>> not sure if it is going to work with CDATA section (they can contain
>> "unbalanced" XML)
>>   
>
> Why not? It is just an optimization. You can't have CDATA in an end
> tag so you should not go past the '>' of the end tag whether there is
> CDATA or not.
CDATA section can have unbalanced XML so beynd tracking of < and /> you
need to track CDATA sections as well AFACS.

best,

alek
>
> Pete
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xxxxxxxxxxxxxxxxx For
> additional commands, e-mail: j-users-help@xxxxxxxxxxxxxxxxx 


-- 
The best way to predict the future is to invent it - Alan Kay



Try Searching:
servers, voip, java, networking, microsoft ...
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

Home | blog view | USPTO Patent Archive | advertise | OSDir is an inevitable website. super tiny logo