Jan Algermissen wrote:
> [apologies for stepping in here with just a short remark, but work will keep me another couple
> of days from thoroughly digging through what has already been built and said]
>
> I think the focus should be on (appropriately used) HTTP and not on primarily on REST. One of the benefits
> a REST-Style architecture offers to an API developer is uniformity. Trying to be too generic (as in 'REST API')
> reduces this benefit. One might build a framework for developing APIs for REST architectures, but when it
> comes to developing the API (is this is what we do here IIUC), sticking as much to the architecture as possible
> yields the greatest benefit. Every design decision we can possibly take away from the developer will make her life
> easier[1].
>
+1, especially on the last sentence (which also reflects my concern over
the use of annotations some cases).
<snip>
> A nice read is Mark's abstract model of HTTP resource state[2].
>
Agreed.
Paul.
> Jan
>
> [1] That is IMHO the great power of Atom as it (when assumed mandatory) narrows the design space even further.
> [2] http://www.markbaker.ca/2001/09/draft-baker-http-resource-state-model-01.txt
>
>
>
>> Marc.
>>
>> ---
>> Marc Hadley <marc.hadley at sun.com>
>> CTO Office, Sun Microsystems.
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
>
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109