In my ongoing work on the Webjay API, the standard way to update an element is to PUT to /api/by/username/playlistname/elementname. Simple and clean in...
... curl -T filename url ? ... *shrug* works for me. The only time I use POST for PUTting is to support browsers, which is only a small part of the systems I...
... And you display the error messages how? and URL-encode the file how? These aren't rocket science, they're just a sign of immature tech. ... I have to be...
Another example of how lowly PUT is fancy: virtually 100% of PUT documentation and related tools think it means to copy a file from the client to the server. ...
... curl -f -T ? ... ?? ... Eek, I think you've got this all wrong Lucas. REST is a guide. It helps you understand, in this case, the costs of using POST to...
... Well, I've never encoded the PUT body itself; unless you're talking about things like content-encoding (which work for PUT the same way as everything...
... Hmm. It's really hard to follow you. Could you please be a bit more verbose about why you consider that wrong? It doesn't need to be a physical file, ok,...
... I am debugging a problem with PUT. PUT data on this server never gets to the handler script. There are many places in the server configuration where the...
... The availability of PUT and DELETE across various toolsets has been extensively cataloged here: http://tinyurl.com/2h54n -joe -- http://BitWorking.org ...
... Hi Mark, I am certain that I do not have this all wrong. My comments here are for people like me who are interested in the work of taking this guide and ...
I confess that I am deeply curious about the real world use of the 101 (Switching Protocols) status code. Is this viable in today's firewall environment?...
... If your point is that GET has better support than PUT -- ok, that's kind of obvious. On the other hand, with the Java servlet API I never ever had any...
... I'm not going to argue abut the premise. I asked in another thread whether there were people interested in a rest-dev kind of list and consensus was for...
... Can't follow. You'll have to accept the fact that people will start to ask questions if what you write things they don't be understand. It's not anybody's...
Hey, ... Well, when you say stuff like "I have to be clear about my motivations here: to get real. We talk about this stuff as if implementation was beneath...
... The thing here is that I'm defending the premise rather than working out the details. The premise is: RESTful design is mature, implementation isn't....
As I said before, bidirectional communication is a security issue for general purpose servers. It should be obvious that the folks who write general purpose...
End result - A link summarizing support of PUT for various clients & servers was found & relayed (thanks Joe) - Lucas still can't use PUT (or can you? let us...
I think the point of the question was that PUT does not require URL encoding in the same way that browsers encode file uploads ("multipart/form-data"). An HTTP...
Hey Mike, Thanks for taking my trollish and incoherent messages at face value. ... Nope. I had to finish the job, so I redesigned to use POST. ... Lucas...
... The HTTPSY protocol uses the 101 status code to initiate a TLS/1.0 upgrade, as specified by section 3.3 of RFC 2817. I'd be interested in any reports of...
I'm looking at an integration of Chiba's XForms implementation into a REST repository. Does anyone have experience with integrating Chiba? (One of the chiba...
Hi everyone, We have a new home for RESTwiki[1]! It uses PurpleWiki[2] which isn't very different than MoinMoin, except that it doesn't use white space for...
