Nikita,
> We have a webapp that needs to support binary updloads from a remove
> fat client: if our client crashes we'd like it to automatically "send" a
> zipped log file to our web application. the delivered file would NOT be
> stored in Tomcat server's file system - but inserted into db.
>
> A
> > Apparently our fat client can issue either a POST or a PUT request. The
> > client developer has a slight preference for PUT. I must admit to not
> > being familiar with HTTP PUTs - are there any downside to using PUTs
> > (aside from having to override doPut())?
>
> I don't think your code wil
Nikola,
> It is also a question of semantics. If the technical side is the
> same, then let us communicate our intentions clearly.
>
> PUT - request that will create an object on the server side,
> accessible via the given URL. Used for object upload.
This is a good point: one of the headers tha
