Re: [wsrp] Caching and doing POST on resource URLs

[Nathan Lipke <nlipke@bea.com>]

In fact any method (verb) can cause the the cached markup to become 
invalid. For better or worse, many forms are written without a method 
attribute causing it to perform a GET.

Nate


Stefan Hepper wrote:
> Since we are in the progress of making some editorial changes :-) here 
> something we just noted:
> 5.2.1.2 states:
> "Consumers should be aware that invoking performBlockingInteraction 
> and/or handleEvents may cause cached markup to become invalid."
>
> I think this should be extended to also include getResource triggered 
> via HTTP method POST, PUT, DELETE as in that case the portlet will 
> likely make state changes that render the previously cached markup 
> invalid.

> Stefan
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.