Ashish wrote:
The idea is to include some well known Protocol (like DNS, HTTP, XML
etc) encoder/decoder in MINA source.
Essentially to speed up the development tasks.
These may be completely functional or may need some work before they
can be used. This shall help in
easy adaptation of MINA for different projects. Users are free to use
them as is, extend them or can use them as reference
to build their own.
Challenges that I see
1. We can't enforce high level object structure on User applications
2. Something unknown that I haven't thought of :-)
Would like to know the opinion of Dev community on this.
Two years ago (more or less), we had a discussion about developing a
project we would have called MinaReal, implementing as much protocol as
possible. The name itself was taken from Ethereal, and it sound pretty
well (a bit like mineral).
The idea wasn't to build a concurrent product to Ethereal (as this
product works directly on the network layer), but much more as a proxy.
So basically, yes, this is a good idea.
You have to know that we already have AsyncWeb (http), FtpServer, Dns,
Ntp, Dhcp, Kerberos and Ldap implemented on top of MINA (even if those
projects are shared between MINA and Directory, for historical reasons).
It would be interesting to give more focus on each of those projects, in
MINA, and to increase the base supported protocols. Another aspect would
be to define some clear API for protocol like LDAP, Kerberos, etc, in a
way it's possible to implement them directly, without having to take
care of the intern of the codec. It's not so easy ...
So +1, definitively !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
