On Wed, Jan 26, 2005 at 09:09:19AM +0100, Roland Weber wrote: > Hi Oleg, > > > I am +1 to try to keep http-common API Java 1.3 compatible. I would not > > worry about http-common-implIO and concentrate exclusively on NIO impl > > until some real J2ME demand materializes backed by a number of > > contributers. > > That was my line of thought as well. The question remains whether we just > *try* to keep the API compatible, or whether we keep the API in a separate > component (or, technically, as a separate build target) so we can build > it against JDK 1.3 to verify the compatibility. > If we consider this a technical question, we can defer the answer until > the implementation begins. On the other hand, we could address it on a > component level in the High Level Component Architecture. > > cheers, > Roland
Roland, As long as there's no real demand for J2ME compatibility I would just *try* to stay 1.3 compatible and revisit this issue before the http-common API freeze. I am a little wary of excessive fragmentation. I see no sense in two class packages (essentially it takes only a HttpParser and HttpConnection impls) and would rather bundle these classes into http-common Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
