>Given only Windows relies on file name extention, it seems that making
>file extention significant is not cross platform. Thus it does not
>belong in a platform-independant specification.
Given that argument, what does it matter what the extension is for non-Windows
platforms? Choosing an extension that is useful on one platform doesn't make it
platform dependent. The servers run on multiple platforms and need a decent way
to tell administrators which files are deployable and which can be ignored,
that's simply a usability statement. If an vendor created web application
contains things other than the packaged archive that is to bedeployed into the
server, we need a simple way to show which files are importable into the server.
Special extensions are the most common way to differentiate between file
types....even on UNIX. If I'm looking through my Linux filesystem and I see a
file named foo.html ....in general, it tells me that it has HTML content in it.
Just because I can't launch it by typing foo.html or double clicking on it
doesn't mean that the extension has no meaning.
-----
Spike Washburn
IBM WebSphere Application Server
Internet E-mail: [EMAIL PROTECTED]
Paul Philion <[EMAIL PROTECTED]> on 07/07/99 09:15:19 AM
Please respond to "A mailing list for discussion about Sun Microsystem's Java
Servlet API Technology." <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Donald Washburn/Raleigh/IBM)
Subject: Re: Comments on 2.2 Public Review Draft
James Duncan Davidson wrote:
> Obviously this isn't useful as being able to double click on a jar file
> and launch an included app is a good thing.
This may be a stupid question, but can a .jar file be "clicked on" by
any other platform than Windows? How do I "click on" a .jar file in
Linux?
> Being able to double click
> on a war file and have your servlet/web-app development tool open it up
> is a good thing.
Again, how do I "click on" a .war file in Linux, using a command line? I
may be old fashioned, but I do everything with "make".
> File extensions, especially on Windows, are the
> differentiator between file types and what should be done with them.
Perhaps that should read "only on Windows". Lunix, Solaris, HP-UX and
other versions of Unix that I am familiar with don't rely on file
extentions (though certain applications, like some graphical file
system, do). I do remember something about "magic numbers" under Unix.
Further, the Mac uses a completely different scheme for associating
files with applications, based on resources.
Given only Windows relies on file name extention, it seems that making
file extention significant is not cross platform. Thus it does not
belong in a platform-independant specification.
Just my opinion,
- Paul Philion
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
