Danny,
cil
>> IMHO the names are intuitive and its only 5 classes. I'd rather keep
>> a flat structure with everything in javax.websocket.* package.
> OK. Well we are balancing the need not to require server API classes
> for rich clients, which really pulls us in the direction of needing a
> separate package to make the separation between the models clean.
Do you expect two separate JARs for client and server or rich clients to
extract the required classes out of a single JAR ?
Arun
>
> We may well have more server specific classes in future releases too !
>
> - Danny
>
>
>
>
--
http://twitter.com/arungupta
http://blogs.oracle.com/arungupta