burtonator wrote:
>
> Rapha�l Luta wrote:
> >
> > burtonator wrote:
> > >
> > >
> > > > Imagine the file is a jsp, cfm, php,... If you don't use the URL, these won't
> > > > be used correctly.
> > >
> > > We need a regular expression entry within JetspeedResources.properties
> <snip>
> > That's a hack ! There's no *correct* way to determine if a URM is dynamic or not:
>
> Yes. It is. I think it is worth it for the performance advantage. It
> would be bad to have content stored in the JetspeedDocumentCache which
> is already on the local webserver and is static. This will mean more
> work for the HTTP server, DiskCacheDaemon, DiskCache and OS (IP stack).
>
Don't think so. Once the fetched the file and put it in cache, you're in a
periodic cache refreshing mode that certainly would stress your HTTP server.
The main disadvantages I see are storage space related, but then storage
is cheap...
> I would *much* rather pull static content directly from the FS if it is
> local.
>
use file:// URLs to refer to local static files.
> > http://myhost/forms/getit/now
> >
> > may be:
> >
> > - a call to a static directory /forms/getit/now which in turn may use
> > index.jsp as its default page
> > - a call to a document with negocitation enabled (look at Apache MultiViews)
> > - a call to the getit CGI with the /now path_info
>
> The point is that if you are developing under Jetspeed. You already
> know what your dynamic content will be. Honestly the default
> http.server.dynamic.content will solve 90% of these cases. We can make
> it clear that this could potentially be a problem.
>
> > Putting all the possible exceptions in jetspeed, require the admin to control his
> > full URI space and reverse its configuration process. And then you still
> > can't handle implicit document calls like (index.jsp) or path info.
>
> Not control his full URI space. Only the URI space they want to publish
> under Jetspeed.
>
This is certainly not true for me. We have more tahn a thousand pages on
our site, with several applications, none developped by the same team. I
don't know for sure when I look at a local URL if it is dynamic or not
without checking.
If a project leader wants to "publish" his pages to Jetspeed and gives me an
URL, I want to be able to register it without worrying about dynamic, static
aliased, implicit URLs...
> Implicit document calls like index.jsp will match through regexp. Path
> info you get for free :)
>
How do you match something that doesn't appear in the URL ?
How do you know thazt some part of an URL is path_info and thus you should
not match against it ?
How do you resolve URL->file with [aliased|redirected|mod_rewrited] URLs ?
How do you know that the .html file you're calling doesn't include some SSI ?
Come on, let's not spend time implementing a mechanism that will fail for 70%
of the requests, nearly every pages are dynamic nowadays...
> > I'm -1 on any trick like these.
>
> Does the above change your mind?
>
Your guess ? ;)
--
Rapha�l Luta - [EMAIL PROTECTED]
--
--------------------------------------------------------------
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]
