users@jersey.java.net

Re: mapping put calls (can't have optional/empty payload?)

From: danomano <dshopkins_at_earthlink.net>
Date: Mon, 7 Jun 2010 15:17:18 -0700 (PDT)

thanx for the quick feedback, yeah, I was pretty sure put was intended to be
all or nothing, I didnt think the 'defined' REST api we came up with was
REST compliant based on that, guess I can use the RFC as evidence to my
claim :)

-- 
View this message in context: http://jersey.576304.n2.nabble.com/mapping-put-calls-can-t-have-optional-empty-payload-tp5151283p5151383.html
Sent from the Jersey mailing list archive at Nabble.com.