Re: [Resteasy-users] Entity ID as POST response header

[Michael M. <mmu...@re...>]

  The url in location header is already unique so why do you need to 
refer to it by another id.

Some rest folk say that urls should be opaque so they would advise 
against parsing it for meaningful information.

Mike


> Hi List,
>
> I have many typical entity resources to which a POST will create a new
> instance and return the resource URL as a Location header.  However, I
> find myself parsing this header in my application clients frequently to
> strip out the ID of the newly-created entity.
>
> While the logic is trivial, I feel like it's silly to do this when I
> control the server logic as well.  I'm thinking about adding and
> Entity-Id header to store the uniqe ID of whatever entities are created
> at the various resources.  Is there any reason why this is bad practice,
> RESTfully speaking?  I would of course leave the standard Location
> header(s) there.
>
> Thanks,
>
> Chris
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App&  Earn a Chance To Win $500!
> Tap into the largest installed PC base&  get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Resteasy-users mailing list
> Res...@li...
> https://lists.sourceforge.net/lists/listinfo/resteasy-users