On 5/17/11 2:33 PM, Markus KARG wrote:
>> Then again, how vague can the spec be on this switch? Can the spec say
>> "Vendor must support HTTP caching, how it does it, or how it is
>> configured is implementation dependent."?
>
> Again, I just want a client to (at least) prevent duplicate requests. So yes, it can be vague
I meant, does it violate any best practice or rule of JSR writing, to
require a feature, but not really define any of the semantics of the
feature.
On more thought I'm kinda changing my mind on this.
1. Generally developers are going to want to specify a vendor-specific
eviction policies and configuration, so I don't see that adding
ENABLE_CACHE provides any benefit to the specification
2. THere's also questions of semantics that break WORA as well. DO you
cache bytes and/or unmarshalled entities. Are the bytes and/or entities
mutable or not? All questions that really need to be answered.
I'm sure there's other issues we haven't thought of that need
specification as well.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com