Roland Weber wrote: > Hi all, > > I also think that changing the JDK requirement for HttpCore > between the last alpha and first beta would be a case of > very poor timing. Even if 1.3 compatibility becomes obsolete, > there will always be mobile devices where the full J2SE is > not available. We can reconsider the minimum requirements > for HttpCore 4.1. > > For HttpClient, I don't care about the minimum JDK level, > as long as you don't expect me to learn Java 5 over night :-) > > cheers, > Roland >
What you most likely want on a mobile device is a simple client to make individual requests to one server. No need for the server side for now (until mobile devices all have an IPv6 address). Support for concurrent requests is purely optional. Of course the MIDP API has a HTTP client built-in. Although the API is crap (timeout handling) and implementations are buggy (chunked TE, char encoding, 100 cont, etc.). But it's built-in and comes at no additional footprint. On J2SE it's a lot better, but it lacks some advanced features. For me the big question is: what are the important features for the mobile platform? What's the reason that you can't use the standard API? On the other hand, computing resources on mobiles will increase and platforms will become more PC-like. For me that means MIDP will eventually be replaced by full J2SE implementations (and .NET). The Android is just one example. So, what's important, is not that HttpClient is compatible with mobile devices. But that you can *build* a specialized HttpClient for mobile devices upon HttpComponents. Please note the completely different networking APIs of J2SE and MIDP, and there is virtually no support for reflection and ClassLoaders, Logging is also a problem. Even JDK 1.3 is a *lot* bigger than MIDP. Thus the core libraries *should* be relatively easy to port/translate/compile to J2ME, while HttpClient's focus can be J2SE exclusively. But I don't think our primary focus is mobile devices (even though they are very important) at the moment. And 1.3 compatibility may somewhat help in porting, but doesn't make it compatible automatically with MIDP. If someone wants to start a MobileHttpClient, go for it - it will get a home under the new TLP. Then we can start to work together on the core libraries, so that they are of the most use for both. Odi -- [web] http://www.odi.ch/ [blog] http://www.odi.ch/weblog/ [pgp] key 0x81CF3416 finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
