splitting the ByteBuffer code out into a separate jar file sounds good to me. I know of some programs that I am working with that do not perform any network I/O could still make good use of a small, stand-alone jar file without bringing along the MINA I/O classes
+1 On 2/16/07, John E. Conlon <[EMAIL PROTECTED]> wrote:
If we split the projects up to additional jars, can we do it so we do not create split packages? (Packages that exist in more than jar.) John Mike Heath wrote: > This would provide a very convenient way to use the MINA ByteBuffer in > AIO without having to depend on all of MINA core. I like this idea a > lot. > > -Mike > > On 1/20/07, Trustin Lee <[EMAIL PROTECTED]> wrote: >> Hi, >> >> The MINA ByteBuffer classes can be used without MINA for easier >> manipulation >> of NIO ByteBuffers. For now, they belong to mina-core JAR, but we could >> split it even further to the two JARs; mina-bytebuffer, mina-core, and >> mina-transport-nio. By this sepration, we could remove some bad cyclic >> dependencies between transport implementation and the core API and allow >> users enjoy the access to the powerful byte buffer manipulation without >> using MINA. >> >> WDYT? >> >> Trustin >> -- >> what we call human nature is actually human habit >> -- >> http://gleamynode.net/ >> -- >> PGP key fingerprints: >> * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E >> * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6 >> > >
-- ..Cheers Mark
