HI all, I currently have a read-only server that exposes some resource uris with query parts like the following:
http://foo.com/bar?a=123&b=456 I now need to implement DELETE and PUT operations over these resources... and I just realized that working on URIs with query variables is a bit messy. Two issues so far: First, suppose I have to implement method tunneling for some clients... that means they will pass a parameter called "method" when POSTing. I digged into the codebase and realized that after the TunnelFilter is applied the reference query is cleared. This means the original URI is modified ( ? )... oops. Second, whenever I want to build these URIs using utilities from restlet ( or almost any other library ) I cannot specify the order in which the parameters get serialized... so I can get any of the following two URIs http://foo.com/bar?a=123&b=456 http://foo.com/bar?b=456&a=123 Which are not equivalent. hmmm... So, any rules of thumb?? avoid query variables on read-write ( PUT-DELETE-GET ) URIs?? Thanks, Aldo -- ::::: Aldo Bucchi :::::
