[Resteasy-users] Entity ID as POST response header

[Chris B. <cbr...@re...>]

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