From: Bill B. <bb...@re...> - 2009-03-30 19:23:42
|
I don't know if there is a need. Looks interesting though. Ryan McDonough wrote: > Because JAX-RS never had a client API in mind, the subject of URI > Fragment Identifiers hasn't really come up. I started thinking about it > because in some situations, you may only need to access a portion of the > data from a given resource. The most common use of URI Fragment > Identifiers is with anchor tags in HTML documents whereby the browser > will scroll the section of a page into view. With XML and other data > types, it usually involves viewing a portion of the resource or select > node of the resource. > > From a RESTEasy client perspetive, you could do something like this: > > @GET > @Path("/{id}.txt#line=10,20") > public String getText(@PathParam("id") String id) {... > > The method would return a String that contains lines 11 through 20 of > the text resource. The challenge with URI Fragment Identifiers is that > they are media-type specific. For example, text/plain has an entire spec > dedicated to it: > > http://tools.ietf.org/html/rfc5147 > > XML and HTML also their own rules regarding URI Fragment Identifiers. > With that said, is there any interest in developing this further? One > way I'm thinking about it is to create a ClientsideInterceptor for that > would lookup a URI Fragment handler for a given media type and process > it accordingly. Thoughts? > > Ryan- > > -- > Ryan J. McDonough > http://www.damnhandy.com > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-developers -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |