I was talking to the author of a book on REST the other day, and noticed
that neither HTTPClient nor HTTPSocket really seem to support REST APIs. At
a bare minimum, I think you'd probably want the ability to add arbitrary
headers to GET/PUT/POST (which HTTPSocket doesn't allow) and the ability to
issue DELETE commands. For example, Amazon's APIs require an Authorization:
header, and writing a clean WebDAV client that didn't duplicate a huge chunk
of HTTPSocket functionality would be impossible at the moment. I'd be happy
to submit a changeset refactoring HTTPSocket to make this more feasible, but
I wanted to verify that I'm not either misunderstanding how these classes
are supposed to be used or missing existing functionality already in the
image.

Cheers,
--Benjamin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20070321/6a5d8520/attachment.htm