Peter,
WAR files are about web-content.
No - WAR files are about web applications, much like SAR files are about
server applications ;)
As such all that's at the root level
of the archive (HTML, JSP, GIF etc) can be said to be the primary
content.
Some people do that but it is a misuse of it. Ideally anything that is not
dynamically generated or an integral part of Web Application should be hosted
behind a real web-server which has faaar better performance characteristerics
and support than any servlet engine is likely to have for a while.
But anyways thats just a pet hate of mine ;)
Perhaps the ideal web server could take a WAR file (with plenty of
static content) and, at load time, hand the static content to some
sister server that is more tuned to serving static content. I stand by
my definition, despite performance concerns, that a WAR's root is for
content and WEB-INF is a convenient place to hide conf, libs & classes.
Stuff in WEB-INF/classes and WEB-INF/lib can be said to be
support. I.e. they are given a namespace (WEB-INF/*) that is unlikely
to be required in the directory structure of the primary content.
SAR-INF/ sounds like support for server applications?
I don't think Phoenix server apps are that category of thing. If I
agree with SAR-INF at all it's to replace the "conf" dir and no more.
The reason is because currently there is no way we can only partially extract
.sars. We need someway to separate support data from other data.
That is, unless someone can come up with an example of a SAR files that
would need the root namespace to the same level as WAR files do.
Almost all servers include documentation, some include sample data for
serving or configuration or whatever. Of all the servers I have installed I
can only think of one (DJ Bernsteins DNS server) that did not come with
application data.
For instance the httpd server comes with sample config files, documentation
and a few other support utilities (like those for creating "encypted"
password files). It is conceivable that James will come with separate mailet
jars, mailet config and docs in future. DNS comes with whole sets of command
line utilities as do the scheduling tools.
Can you think of any server applications that don't (or shouldn't) have this
sort of data? If not would you have these installed separately?
It was not about that Pete. Of course I understand that servers come
with conf and a miriad of jars. My point was simply that stuffing
everything into SAR-INF looks daft and more like an imitation of WAR
files. However, I'm not a do-er in this area of Phoenix, so feel free
to ignore my comments.
- Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
