Side navigation
#10287 closed enhancement (plugin)
Opened September 15, 2011 07:40PM UTC
Closed September 20, 2011 02:42PM UTC
AJAX: Implemention of ifModified attribute for pushing changes to server
| Reported by: | nemesis02 | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | None |
| Component: | ajax | Version: | 1.6.4rc1 |
| Keywords: | Cc: | jaubourg | |
| Blocked by: | Blocking: |
Description
Implements If-Match, and If-Unmodified-Since request headers under POST, POST and DELETE types since If-Modified-Since and If-None-Match are mainly retrieval operations.
Attachments (0)
Change History (4)
Changed September 16, 2011 02:33PM UTC by comment:1
| cc: | → jaubourg |
|---|---|
| component: | unfiled → ajax |
| priority: | undecided → low |
Changed September 16, 2011 03:53PM UTC by comment:2
Everything is in "mainly". It should be pretty easy to implement this behaviour using a prefilter. Come to think of it, the ifmodified option could and should actually be handled that way.
I'm really not convinced here. I'd be tempted to tag it ajaxHooks... if there was such a tag.
Changed September 17, 2011 04:51AM UTC by comment:3
the current tags that are in there apply for the retrieval of data only under the ifmodified attribute, the post versions don't make sense if you say them out loud from a version control perspective. You want to push a change if an etag matches that to which you last retrieved, not if etag doesn't match. Similar behaviours just different purposes, or direction to which the data is going. If an etag does not match via post, it means the data has changed since the last time that user retrieved the data and he should update his request to ensures latest changes are saved and data isnt overwritten.
Changed September 20, 2011 02:42PM UTC by comment:4
| resolution: | → plugin |
|---|---|
| status: | new → closed |
We'll keep this as implementable in a prefilter.
Deferring to jaubourg for thoughts on this.