Call me thick, but I feel unable to make up my mind without an
example of how this is intended to be used. Is the sample
implementation published a while ago still close enough, or should I
look at something newer?
Stefan
--
Stefan Tilkov, http://www.innoq.com/blog/st/
On Apr 16, 2007, at 5:39 PM, Marc Hadley wrote:
> On Apr 13, 2007, at 3:17 PM, Marc Hadley wrote:
>
>> On Apr 13, 2007, at 1:21 PM, Jerome Louvel wrote:
>>>
>>> That's an interesting path to explore. I'm still not found of the
>>> Response
>>> class and subclasses, but I'm interested to look at an updated API.
>>>
>> Sure, I'll also try to roll in some of the feedback received so
>> far and post some updated javadocs early next week.
>>
> See:
>
> https://jsr311.dev.java.net/sketches/sketch1/overview-summary.html
>
> The java.net infrastructure seem to interfere with normal frames-
> based javadoc viewing so for now you'll have to use the non-frames
> pages or checkout the "sketch1" branch from Subversion.
>
> Main changes:
>
> - Removed some of the SPIs
> - Coalesced some packages
> - Refactored HttpContext, HttpRequestContext and HttpResponse.
> HttpContext becomes an annotation that can be used to inject
> UriInfo, HttpHeaders and PreconditionEvaluator.
> - Added a few new annotations for marking properties that
> correspond to HTTP metadata
> - Reworked Representation and HttpResponse to use annotations to
> mark their properties as I'd outlined earlier in the thread.
> Essentially the representation and response classes become "pre-
> baked" instances of return types but the annotation approach allows
> an application to use their own classes instead if they so wish.
>
> I have some concerns about the rework described in the final bullet
> - I'll air those shortly in a separate mail.
>
> Marc.
>
> ---
> Marc Hadley <marc.hadley at sun.com>
> CTO Office, Sun Microsystems.
>
>