Sorry. Its not a HashMap, but a TreeMap.
http://mina.apache.org/report/1.1/xref/org/apache/mina/example/httpserver/stream/HttpProtocolHandler.html#69
TreeMaps use natural ordering, so I am still not sure that ordering can be
guaranteed. The reason I mention ordering is that when you pull the
information out of the TreeMap, it might not come out in the same order in
which it was put in.
I hope this clears up my previous statements.
On 4/12/07, Eugene Labunsky <[EMAIL PROTECTED]> wrote:
Dear Mark,
I've added output to the STREAM example (just Main & HttpProtocolHandler
classes).
In this sample I can't see any HashMap, just write to PrintWriter and
finally flush & close it (I keep all sample just added those 2 lines of
code
for output 1024 lines).
Could you advise me, where is problem?
>Based on previous discussions on this mailing list, I think that the
>'codec' based HTTP example is the preferred method. If you are
>placing each line in to a HashMap as per the example, this could be
>your problem because HashMaps do not guarantee order. Check the API
>javadocs for more information.
--
..Cheers
Mark
On 4/12/07, Eugene Labunsky <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have problem with http stream output.
> I have project based on http stream sample and found that MINA can't
> output
> more than 200 lines http reply correctly. It mixed lines in reply ;(
First
> time it reply correct, then not. I have added small peace of code to
> public
> void run() in sample:
>
> for (int i=0;i<1024;i++)
> out.println("<p>this is line: " + i+"</p>");
>
> And ... With all available MINA releases I have problem. MINA can reply
> correctly or from 284 lines... Please, let me know where I'm wrong...
Regards,
Eugene Labunsky.
--
..Cheers
Mark
