I didn't get a chance to do this but I've a bit more time to pick it up. I originally used jetty websockets but I was keen to pick up Moxie's code instead to avoid having to replicate what the framework was doing when handling websocket requests.
@moxie how do you see the relicensing working? Btw, in our app we also needed MQTT so I dropped in Moquette which gives us websockets too with authn and authz, I could share that too if people were interested. On Tuesday, 14 June 2016, Moxie Marlinspike <mo...@thoughtcrime.org> wrote: > > Hey Tim, I'm not sure if anything ever happened, but I'm still totally > willing to relicense if you want to package this up into dropwizard. > > - moxie > > On 06/13/2016 03:51 PM, Tim Bartley wrote: > > hi Graham and moxie, > > > > At the risk of replying again to a very old reply to a very old post ... > > > > Was any progress made in making this DropWizard extension available > > under an Apache license? I, too, am in a gig where this extension to > > DropWizard would likely be perfect but unfortunately we can't consumed > > AGPL'ed code. > > > > I probably have some capacity to assist if that's a useful thing? > > > > Cheers, > > > > Tim > > > > On Thursday, December 10, 2015 at 8:59:48 AM UTC-7, Graham O'Regan wrote: > > > > Sure, we wouldn’t pull it into core, it would be a module instead. I > > used dropwizard-websockets for my initial implementation but > > @moxie’s design allows annotated resources and incorporates > > authentication so it is quite a bit more advanced. > > > > > >> On 10 Dec 2015, at 15:51, babc...@umich.edu <javascript:;> > <javascript:> wrote: > >> > >> I don't know if it's possible, as I haven't looked at the code, > >> but instead of integrating WebSocket-Resources into the main > >> dropwizard code, is it possible to incorporate it as a dropwizard > >> module? I think that might be the best solution. > >> > >> Additionally for using websockets in dropwizard there is > >> the dropwizard-websockets > >> <https://github.com/LivePersonInc/dropwizard-websockets>, which > >> may suit your needs. > >> > >> And for an entirely different solution, there is a HTTP 2.0 server > >> push pull request, which'll allow you (theoretically) the same > >> functionality as websockets. > >> > >> Anyways, neat project! > >> > >> On Saturday, November 15, 2014 at 2:47:14 PM UTC-5, moxie wrote: > >> > >> > >> Recently I've been using WebSockets more often in some of my > >> projects. > >> It hasn't ever felt great to me, since I have a set of nice > >> Jersey > >> Resources for my HTTP API and then essentially a raw Servlet > >> for my > >> WebSocket API. > >> > >> I ended up putting something together to make Jersey-style > >> Resources > >> available over WebSockets, which I've broken out into a > >> project called > >> WebSocket-Resources: > >> > >> https://github.com/WhisperSystems/WebSocket-Resources > >> <https://github.com/WhisperSystems/WebSocket-Resources> > >> > >> It basically defines a set of interfaces for a WebSocket > >> sub-protocol > >> that is logically similar to HTTP, and then hooks incoming > >> requests into > >> Jersey -- translating responses from Jersey back into the > >> WebSocket > >> subprotocol. > >> > >> This allows you to write a Jersey Resource that you can expose > >> both over > >> HTTP and a WebSocket, unmodified. You can implement your own > >> subprotocol wire format, or use the default protobuf-based one > >> that > >> WebSocket-Resources includes. > >> > >> Obviously bi-direction communication is a big part of > >> WebSockets, so the > >> server can also act as a "client" that issues requests and > >> processes > >> responses. Essentially, both the client and server are each > >> simultaneously "client" and "server" that make REST style > >> requests and > >> get responses. > >> > >> It's working out well for me so far, and actually feels pretty > >> neat to > >> use. I was thinking this is the kind of "glue" that could be > >> a fit for > >> Dropwizard. If you guys are interested in including this or > >> something > >> derivative of this into Dropwizard, I'd be happy to relicense > >> it and do > >> the work to get it in. > >> > >> Thanks, > >> > >> - moxie > >> > >> -- > >> http://www.thoughtcrime.org <http://www.thoughtcrime.org/> > >> > >> > >> -- > >> You received this message because you are subscribed to the Google > >> Groups "dropwizard-dev" group. > >> To unsubscribe from this group and stop receiving emails from it, > >> send an email to dropwizard-de...@googlegroups.com <javascript:;> > <javascript:>. > >> For more options, visit https://groups.google.com/d/optout > >> <https://groups.google.com/d/optout>. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "dropwizard-dev" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to dropwizard-dev+unsubscr...@googlegroups.com <javascript:;> > > <mailto:dropwizard-dev+unsubscr...@googlegroups.com <javascript:;>>. > > For more options, visit https://groups.google.com/d/optout. > > -- > http://www.thoughtcrime.org > > -- > You received this message because you are subscribed to the Google Groups > "dropwizard-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dropwizard-dev+unsubscr...@googlegroups.com <javascript:;>. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
