Re: addEventlistener question

Jacob Kjome wrote:

>I think it is a function of the browser.  Unless I'm mistaken, no
>current browser supports HTTP PUT.  They only support GET and POST.
>That is the reason that when using, for instance, the Tomcat manager
>app, you can't "deploy" your .war via the browser, only "intall" or
>upload a .war file using HTTP POST (in recent Tomcat-4.1.x versions).  The only way to do
>this (without writing your own program) is by using the Catalina Ant
>manager "deploy" task.
>
>I'm not sure we should even have HTTP PUT enabled?  In fact, it would
>have cleared up this issue from the get-go.  We have to understand
>the behavior of HTTP PUT as far as how parameters are passed before we
>allow its use.  We are
>all famililar with POST and GET and should probably limit Barracuda to
>that until we actually understand how to support PUT.  The other
>option is to detect the client and ask if it actually supports PUT.
>If not, we return an error page stating the lack of client support.
>

PUT is a method that has to be enabled in the webserver - then it allows 
for the replacement of the url by the data transimitted using the same 
mechanism as POST. I once set up an apache to accept PUT (AFAIK you got 
to specify a cgi for it). Then when somebody in the intranet openend a 
page with the netscape composer, it could be published directly, without 
messing around with ftp or shared harddrives.

This was 5 years ago, and my impression is that the mechanism is fairly 
abandoned and replaced by webdav, as that allows for more control.

Conclusion: We don't need it :)

Diez