Comments on: Addressability of Fragments http://www.subbu.org/blog/2008/02/addressability-of-fragments HTTP, REST and some Cycling Fri, 12 Mar 2010 22:08:31 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Subbu Allamaraju http://www.subbu.org/blog/2008/02/addressability-of-fragments/comment-page-1#comment-223 Subbu Allamaraju Mon, 25 Feb 2008 14:33:03 +0000 http://wp.subbu.org/2008/02/addressability-of-fragments/#comment-223 >> As long as you only think of a resource as a 'full document' or some other type thing, fragments will be an issue. Well said. >> Of course the server has some work to do sorting out what is addressed and how to keep the data in sync, but that's where this *should* happen - not on the client. Well said, again :) >> As long as you only think of a resource as a ‘full document’ or some other type thing, fragments will be an issue.

Well said.

>> Of course the server has some work to do sorting out what is addressed and how to keep the data in sync, but that’s where this *should* happen – not on the client.

Well said, again :)

]]> By: Mike Amundsen http://www.subbu.org/blog/2008/02/addressability-of-fragments/comment-page-1#comment-222 Mike Amundsen Mon, 25 Feb 2008 14:28:16 +0000 http://wp.subbu.org/2008/02/addressability-of-fragments/#comment-222 In my experience, this discussion of 'addresssable fragments' comes up when folks are not clear on the true meaning of 'resource.' I think of a resource as an abstraction of some data on the server. As long as you only think of a resource as a 'full document' or some other type thing, fragments will be an issue. But if you do as you suggest (make the target addressable), then we need to deal with fragments. Of course the server has some work to do sorting out what is addressed and how to keep the data in sync, but that's where this *should* happen - not on the client. In my experience, this discussion of ‘addresssable fragments’ comes up when folks are not clear on the true meaning of ‘resource.’ I think of a resource as an abstraction of some data on the server. As long as you only think of a resource as a ‘full document’ or some other type thing, fragments will be an issue.

But if you do as you suggest (make the target addressable), then we need to deal with fragments. Of course the server has some work to do sorting out what is addressed and how to keep the data in sync, but that’s where this *should* happen – not on the client.

]]>