Ok about UDP now ;) there is a session automatically created for each source point (ip/port), and a sessions recycler for destroy them, because UDP have no connect/disconnect mechanism like TCP.
You have a iosession.write method which take another argument for the destination address. No support for UDP multicast (not supported in NIO, will be in NIO2). Julien On Fri, 30 May 2008 11:02:25 +0200 "Daniel Wirtz" <[EMAIL PROTECTED]> wrote: > Because FastCGI became boring, I am currently implementing DNS on top > of Mina. I noticed a few discussions about UDP lateley, so, is there > something special I need to know about it in Mina or can I use it > just like I would use TCP? > > What happens to UDP messages that got split? Is there always a new > session created for every message that comes in? As of the nature of > UDP I guess so or does Mina handle this internally using the > ip:sourceport pair? If not, what and where is the best way to > circumvent this? > > Btw. it would be nice having Mina (2.0) to support various standard > protocols like these out of the box, I guess this would increase > popularity drastically over all the other frameworks. I don't think a > complete application handling the decoded messages is required, but > having decoders for HTTP (already there and pretty), FTP (also, but > looks more like a complete application), FastCGI, DNS, SMTP, IMAP, > XMPP (not a server, no special XEPs, just a rock solid basic protocol > de-/encoder) etc. would be a really good starting point so that > everybody can create cool applications on top of it without having to > struggle with de-/encoding (I no more belive in a generator for this > btw.). It's also much easier and less failure prone to implement an > application than a de-/encoder. > > regards > Daniel
signature.asc
Description: PGP signature
