Netty Application hosted on internet

[Trustin Lee (이희승)]

Hi Manish,

I think there's more chance of:

  * packet fragmentation and assembly
  * unexpected disconnection (more frequent connection reset by peer)
  * unnoticed disconnection (client or server doesn't notice the
disconnection until it writes something)

The first issue will appear in localhost under load, so you should
have covered it already.  The second one is OK to ignore IMHO, because
you need to write your application robust enough to deal with an
unexpected disconnection.  The third one might not appear in the
localhost testing - you usually send a periodical ping message to a
remote peer to detect the dead connection.

That's all I can think of at this moment.

On Sat, Dec 27, 2008 at 3:17 AM, manish_iitg
<excellencetechnologies08 at gmail.com> wrote:
>
> Hello,
>
> I have developed a file upload application using netty. but, currently i
> have only tested it on localhost. Can you tell me what all i should take
> care of before i test the application on a hosted server on internet. What
> all unexpected errors can occur when the server is hosted on internet
> --
> View this message in context: http://n2.nabble.com/Netty-Application-hosted-on-internet-tp1922335p1922335.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
>
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>
>



-- 
Trustin Lee, Principal Software Engineer, JBoss, a division of Red Hat
--
what we call human nature in actuality is human habit
--
http://gleamynode.net/