Santiago Gala wrote:
> "Juan C. Alvarez" wrote:
>
> <snip>
> If we try to allow for remote "local" files (via HTTP), I think there
> should be a prefix in the configuration, instead of using fixed values
> like localhost, 127.0.0.1, or <hostname>. This way, in some place they
> could have a dedicated server serving local content (psml, xsl, static
> files, channels) to a farm of machines that would serve the users.
>
I have tested it, using http://xxx:xxx/content instead of /content and it
works fine. In fact, I used a different server (Jigsaw) running in port 8001
in teh same machine. Performance did not looked worse.
>
> There remains to be solved a reasonable way to allow writable resources
> (i.e. customize, jetspeedcontent, ...)
>
I have tested the possibility of using HTTP PUT (using jigsaw, that allows
"putable" files). I got a partial success. There are two problems: security
(we should use a password to allow writable resources), and availability of
PUT method in Apache/JServ/Tomcat. I'm quite sure that Tomcat does not work
with PUT.
Anybody knows for the rest?
In any case, any other idea on how to "put"/"post" a modified resource in
the resource server?
>
> >
> > Thanks,
> > J. Carlos
> >
<more snip>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
