Karl Berry wrote: > Does classpath(x) aim to include only the standard java.* and javax.* > libraries? Or does/can it go beyond that? > > We (GNU) were just offered a small library that implements the websocket > API in a straightforward way, namely websocket4j > (http://students.mimuw.edu.pl/~ms262969/maarons/wsgi.py/software/WebSocket4J/ > http://students.mimuw.edu.pl/~ms262969/websocket4j-1.3.tar.gz > comments welcome). I don't think it is part of any standard library > yet. So I'm wondering if it would make sense to incorporate it into > classpath(x) or if it's better off as a standalone package, at least for > now. Classpath aims to provide the J2SE library API. ClasspathX aims to provide the J2EE library API. These do include some packages beyond those in the java.* and javax.* namespaces, including e.g. org.xml.sax.* and org.w3c.dom.* however it's only the standard APIs we're implementing. We do have a separate network protocols utility package called inetlib, perhaps it would be better contributed to that project? -- Chris Burdess
