After much thinking... I have decided to change the way we resolve URLs
within the disk cache:
Under the current mechanism, if Jetspeed detects that you are using a
local URL such as /tmp/test.xml if will resolve this to a file and serve
that directly -> /usr/local/apache/htdocs/tmp/test.xml
This has the following problems:
- The URL could be dynamic content and not a file. It could actually
just be a servlet and they only way to fetch this would be to go through
the webserver directly.
- The URL would have to be resolved. Because of the differences in spec
between Servlet 2.0 and 2.1 this is a very buggy area within Jetspeed
operation.
- There are numerous file:// URL bugs between JDK versions and Operating
Systems. (even JDKs on the same OS behave differently). Removing and
reducing this will increase reliability.
The new solution will remove all the above problems by just going
through the webserver. The only downside is that under large loads
Jetspeed could get slower (estimated 10% or so). If this is an issue it
could be fixed in later versions.
The new mechanism will remove at least 3-4 known bugs. This will make
it into 1.2b2.
Kevin
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
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]
