Fabio Tudone

`comsat-redis` implements [Jedis](https://github.com/xetorthio/jedis) only partially at this stage and, being a very young integration and notwithstanding the port of the test suite, there might well be serious bugs (e.g. performance...

Here are a few ideas: - Using it in a real-world scenario as @pron suggested and providing improvements / fixes as PRs (best option IMO) - Concurrency / load tests...

[I read](http://www.oracle.com/webfolder/technetwork/tutorials/obe/java/basic_grizzly_jersey/jersey-grizzly-json-service.html) [Jersey](https://jersey.java.net/) can run on [Grizzly](https://grizzly.java.net/) but I don't think Grizzly offers a servlets container personality and `comsat-jersey-server` builds upon `comsat-servlet`, so I think at present you can't have...

Can you share the POM (or even better a small project) that triggers the problem?

@naivefun Does it still happen? If you can't share a project or a POM, what's your project setup? Is there a chance that you have Kryo version conflicts or classloading...

Sorry for the late reply. We haven't started thinking about how to implement it yet but of course ideas and contributions (of any kind) are always welcome. Have a look...

Ok let's keep in touch then, as soon as we think of an API we can organise. Thanks!

@victornoel Could you also add corresponding test cases when you work on the PR? Thanks, expanding test (and use case) coverage is always a great thing.

You can use JSR-356 WebSockets through the Web Actors API http://docs.paralleluniverse.co/comsat/#web-actors. The relevant artifacts are `comsat-actors-api` and `comsat-actors-servlet`.

@cnsgcu Is this adequate to your needs?