Skip to main content

Blog Archive for survivant during August 2010

I want to let you know that since the release of Caucho Resin 4.0, Atmosphere applications can be deploy on Resin and will be supported natively. Resin 4.0 implements Servlet 3.0. That's really good. Another web server that is supported. What about the Websocket's Caucho implementation... nah ! There implementation is too buggy right now. I suppose the code it using a early release of the...
Just a little note that we try to add Websphere native support for Atmosphere. We work really hard to find an API that could allow us to do that, but is simply impossible. We were able to get in touch with the dev team of Websphere and the dev team of WebSphere Application Server Feature Pack for Web 2.0. They have demo that used bayeux for comet application or JMS to simulate asynchronous...
Just to let you know that Grizzly Deployer was adopted (almost) by another framework : Akka. Since May 22, 2010, viktorklang is working in a branch : deployer. here the description in the commit "Starting to add Deployer [viktorklang]" You can browse the code on github : http://github.com/jboner/akka/tree/deployer/akka-core/ I hope to see that included in a next release. You can follow me on...
Just to let you know that Grizzly Deployer was adopted by another framework : Atmosphere. Since Atmosphere-0.6, Grizzly Deployer is in the module : spade-server To launch Atmosphere application you could use Grizzly Deployer or use Atmosphere-Spade-Server (that used Grizzly Deployer under the hood). You can browse the changes on github : http://github.com/Atmosphere/atmosphere/tree/master/...
It has been a while since a blog about Grizzly, I was too busy adding new features. The Grizzly Deployer's community grows and requested theses new features. Here a quick list of the changes : Websockets support Watch folder Can starts without applications to deploy Can be embedded and extended easily and few bug fixes (thanks to the community) A little overview or remainder of what is...
CONTEXT I want to share a problem that we had in our project. We were doing a real-time "Profits and Loss" server (P&L). The server sends stock updates to all the users subscribed to the stocks, basically as Google Finance or Yahoo Finance. SIMPLE IMPLEMENTATION I will used a basic approach (no aggregation and no optimization) to explain the problem that we had with Serialization and...