Folks I think our Jakarta REST client experiment turned out quite well. I am, for one, very happy with the results. With less than a dozen of classes we now have a facade based on standard and widely used APIs that, I gather, should cover the greatest majority of use scenarios of what people use HttpClient for.
It should also help reduce the widespread abuse of the async APIs when users exchange messages with blobs of binary of character data buffered in memory just to convert the damn thing to a JSON object later on. Jakarta REST client should make this anti-pattern obsolete. Now, I am very tempted to build a similar facade for our server side code. This is not an easy decision to make, though, as it would the project into a new territory where we can find ourselves overlapping with long established projects that historically have been quite friendly to us (such as Spring). There are multiple paths here that we can take ranging from abandoning the idea from the start to creating a new server focused project on the same level with core and client, or something in between. What are your initial feelings about this idea? Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
