Paul Fisher wrote:
>
> classpath.tar.gz (everything)
> classpath-core.tar.gz (java.*)
> classpathx.tar.gz (javax.*)
> classpathx-comm.tar.gz (javax.comm.*)
> classpathx-servlet.tar.gz (javax.servlet.*)
> etc.
>
> There's also the option of having just classpath.tar.gz (java.*) and
> classpathx.tar.gz (javax.*).
This sounds reasonable. Two points though:
- one the one hand people sometimes just need one extension and are not
interested in other extension classes
- on the other hand the servlet.tgz file is in its current undocumented and
untested phase only 14 kb. This might grow to something like 50kb but it won't
become very big so making a seperate package for it... I don't know.
> Ideas? Thoughts? Comments? Are we taking on too much?
About taking on too much: I'd say stick to the core library classes, and only
add things like extension classes when somebody drops them on your doormat.
my $0.02 in this matter
a request:
I've uploaded the servlet classes to
http://www.euronet.nl/~pauls/classpath/classpathx-servlet.tgz
Could somebody more knowledgeby then me into the working style of the
classpath organization take a quick looksee and tell me what he or she thinks
of them?
regards,
Paul Siegmann
