True.
Having 2 different ones just seems so awkward to implement.
Guess having 1 websocket class with both annotations wouldn't be harmful,
if it would support being on either end.
Guess we just have to double-up the encoders/decoders/subprotocols
declarations.
--
Joakim Erdfelt <joakim_at_intalio.com>
webtide.com <http://www.webtide.com/>
Developer advice, services and support
from the Jetty & CometD experts
eclipse.org/jetty - cometd.org
On Wed, Feb 13, 2013 at 4:01 PM, Jitendra Kotamraju <
jitendra.kotamraju_at_oracle.com> wrote:
> On 02/13/2013 09:46 AM, Joakim Erdfelt wrote:
>
> It seems that Client side only websockets cannot be annotated with
> @WebSocketEndpoint as that is now a server side only annotation.
>
> Are we going to get an annotation for the client side too?
>
> There is already one: @WebSocketClient
>
> Or can we get a unified annotation for both?
>
> --
> Joakim Erdfelt <joakim_at_intalio.com>
> webtide.com <http://www.webtide.com/>
> Developer advice, services and support
> from the Jetty & CometD experts
> eclipse.org/jetty - cometd.org
>
>
>