Mailing-List: contact users-help@mina.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@mina.apache.org
Received-SPF: pass (athena.apache.org: domain of ayyagarikiran@gmail.com
 designates 209.85.217.17 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=WggxVhHr6JIknaU5GVZAtWqhbYaMjcaaJllmGAyRxTIOy2LoobuowYDdPA0FG8ZqlU
         B2laIAkctlanqsD+xYpRidQMBZHj6IvtxN4bh1NiZ6vmXwwlbVl6PxTb1wUSOvt4h2Ld
         DESiCTdRZe2MbWaFJi6J6a20hUMa/NyV1tGw0=
Message-ID: <4900958A.10905@gmail.com>
Date: Thu, 23 Oct 2008 20:47:30 +0530
From: Kiran Ayyagari <ayyagarikiran@gmail.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: users@mina.apache.org
Subject: Re: MINA - design guidelines
References: <706475.33500.qm@web53503.mail.re2.yahoo.com>
	 <cc4022060810211036o4a261abepef95e562328e95ac@mail.gmail.com>
	 <20098916.post@talk.nabble.com>
	 <cc4022060810211533n7028795eg1bc853edd012c8b@mail.gmail.com>
	 <f404ff2d0810212142l674ddf3ej9b46041dabac3bb5@mail.gmail.com>
	 <20110316.post@talk.nabble.com>
	 <BC6AA927-FC6E-44CF-8599-1260EDF6EAF1@gmail.com>
	 <48FF5AE9.3080305@nextury.com>
	 <f404ff2d0810230558r3331dcb6h13632c4cdf50ef9a@mail.gmail.com>
	 <490080D9.8030608@nextury.com>
 <f404ff2d0810230802v4de03454t2526d7ae34fa40bb@mail.gmail.com>
In-Reply-To: <f404ff2d0810230802v4de03454t2526d7ae34fa40bb@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

How about using a xml pull parser http://www.xmlpull.org/. ( I have used 
it for reading the xmpp stanzas from a socket in a toy xmpp server impl )

Kiran Ayyagari

Ashish wrote:
>> Sounds like a pragmatic approach. If you _know_ that your XML messages will
>> be simple, and that you can detext the closing tag whatever data and
>> comments you will have into your XML, and that you can afford some bad
>> input, that's just a fine approach.
>>
>> <snip/>
>>     
>
>
>
>   
>>> 3. My limited knowledge of IoBuffer class has made code more cryptic
>>> than it should have been :-)
>>>
>>>       
>> The IoBuffer class is just a wrapper (a proxy) on top of ByteBuffer. Every
>> BytBuffer method is available in IoBuffer, but you have a few more
>> functionalities, one of them is that the IoBuffer is extensible (for the
>> record, it would have been much easier to extend the ByteBuffer class to
>> offer this functionality, but, sadly, this class can't be extended, as the
>> constructor is not public ...). So if you know how to deal with ByteBuffer,
>> you should be confortable with IoBuffer.
>>     
>>> I am inclined towards using regular expression for parsing and will
>>> post the code if I am able to do that.
>>>
>>>       
>> You can also use JAXB with a byte stream unmarshaller (but a one which will
>> be statefull). You may have to write your own unmarshaller, i'm afraid (but
>> i'm not a specialist, so anyone with better knoweldge, please catch the ball
>> ;)
>>     
>
> Well the problem of getting multiple xml mesages back to back, was
> what I was trying to resolve.
> But couldn't, coz, again didn't knew how to remove the read part from
> IoBuffer, once the trailing message was detected
> and if it continued for a while my System would be out of memory, I guess.
>
> BTW, when does the IoBuffer gets free up?
>
> Using an XML parser would be like too much, coz it would parse and
> throw parse exception each time the xml was incomplete
> and if the IoBuffer had trailing xml message, it won't parse crying
> about invalid message :-(
>
> Again performance becomes critical. If anybody intent to use a similar
> implementation, VTD-XML parser (http://vtd-xml.sourceforge.net/) will
> be worth evaluating.
>
> I need to do some homework on IoBuffer/ByteBuffer, like how to copy
> chunk from middle (something like substring)
> and how to remove the mark once it's set. :-)
> Long way to go
>
>
>