Re: AsyncHttpClient with no content-length header

disregard the change i mentioned in the previous post .. it won't help. Since there is no CRLF at the end of Body. We would need a Decoding state that reads till session close. I couldn't find a suitable Decoding state present (am new to the code and thats why perhaps could have overlooked

Re: AsyncHttpClient with no content-length header

Thanks Jeff. have raised a JIRA. https://issues.apache.org/jira/browse/DIRMINA-487 While it is being fixed, is there anything i can look at to fix the issue (even if temporarily) ? would really appreciate if someone can help me work out a fix. vishal jgenender wrote: Yes, please open a

[jira] Created: (DIRMINA-487) Fix HTTP response with no content-length header

Fix HTTP response with no content-length header --- Key: DIRMINA-487 URL: https://issues.apache.org/jira/browse/DIRMINA-487 Project: MINA Issue Type: Bug Components: Protocol - HTTP,

Re: AsyncHttpClient with no content-length header

Yes, please open a JIRA on this. According to the HTTP spec, anything with content should have a content line. However, there does appear to be a site that is not compliant (http://www.toptable.co.uk/) and probably more... thus we could fall back to reading until there is no more data. However,

DNS Client (UDP/TCP 53)

Sorry if this is a bit off topic. Has anyone used MINA to build a DNS client? I'm interested in doing nslookup type stuff from Java. cheers, Cameron

Multi-thread/single-session and multi-thread/multi-session, which performances better?

Hi there, I'm looking to write a client-server application which has a multi-threaded client (2500+ threads per client). Each thread needs to send and receive messages with the server, though the sending frequency is pretty low(2-3 messages(of 1k bytes each) per minute per thread). I just wonder

[jira] Updated: (DIRMINA-487) Fix HTTP response with no content-length header

[ https://issues.apache.org/jira/browse/DIRMINA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal updated DIRMINA-487: --- Description: HTTP/1.1 responses (content part) which have the content-length header missing are not

Re: Multi-thread/single-session and multi-thread/multi-session, which performances better?

Hi Qi, On Dec 6, 2007 12:17 PM, Qi [EMAIL PROTECTED] wrote: Hi there, I'm looking to write a client-server application which has a multi-threaded client (2500+ threads per client). Each thread needs to send and receive messages with the server, though the sending frequency is pretty low(2-3

Re: a request about Mina

On Dec 6, 2007 12:03 AM, Mehdi Nikfarjam [EMAIL PROTECTED] wrote: Dear Mr. Lee I am a new Java developer, I have just visit your Introduction to MINA presentations on your homepage, and i found it very interesting, but i have some ambiguity about Overload detector, Could you please

Re: Managing large number of Connectors

Hi Vishal, On Dec 4, 2007 7:02 PM, Vishal_Jain [EMAIL PROTECTED] wrote: Hi All, Am having a bit of confusion and appreciate any help from the community. i want to manage a large number of connectors (which would connect to different web servers). Am experimenting with Mina 2 and use the

Re: queries about mina and proxy

Hi Anshuk, Please do not e-mail me directly. Sending a message to me directly doesn't mean fast response at all. Always use our support forum or mailing list, even if the response is not showing up. On Nov 30, 2007 4:07 PM, Anshuk Pal Chaudhuri [EMAIL PROTECTED] wrote: Hi Trustin, I got

Re: Managing large number of Connectors

Hi Trustin, Yes i did try to follow the Thread model tutorial. As is evident, its not clear to me :) I seem to have missed to understand, One Connector tied with one I/O handler. Thanks for clearing that up for me. now, for every session that is created by calling connector.connect(), i need

Re: Managing large number of Connectors

Hi Vishal, On Dec 6, 2007 2:53 PM, Vishal_Jain [EMAIL PROTECTED] wrote: Hi Trustin, Yes i did try to follow the Thread model tutorial. As is evident, its not clear to me :) I seem to have missed to understand, One Connector tied with one I/O handler. Thanks for clearing that up for me.