Iliyan Peychev Hace 12 años Very nice, David, finally we have something working!The first two potential use cases - to write a mobile site or a new frontend using this approach are really interesting - will be happy to participate!Talking about improvements, what if we replace the HTTP connection with AMQP, for example?https://github.com/postwait/node-amqp Por favor identifíquese para votar. Contestar como... Cancelar
Rushikesh S Thakkar Hace 12 años Looks interesting. I myself having worked with Liferay, and currently working on Node.js keep thinking of use-cases where these two can be brought together. The scenarios you suggested uses Liferay as content provider for Node.js. A scenario I thought of is other way around:Socket.io + Node.js (on backend) with Liferay (on frontend): to display real-time streaming data (stock feeds, clock/time, monitoring dashboard, etc). Por favor identifíquese para votar. Contestar como... Cancelar David Truong Rushikesh S Thakkar Hace 12 años That sounds interesting.I would like to find a way to not have to run 2 different servers. Por favor identifíquese para votar. Contestar como... Cancelar Rushikesh S Thakkar David Truong Hace 12 años @David,I agree with you on that. I too wouldn't like to run 2 different servers. We can use comet libraries for Java - like Grizzly (http://grizzly.java.net/), but websocket support is not yet available in IE and webkit (AFAIK). That's where socket.io comes to rescue.Moreover, Node.js is fares well on high load (plus: has good support for no-sql dbs like MongoD. So I wouldn't mind considering it as a backend for a Liferay app that renders realtime data. Por favor identifíquese para votar. Contestar como... Cancelar
David Truong Rushikesh S Thakkar Hace 12 años That sounds interesting.I would like to find a way to not have to run 2 different servers. Por favor identifíquese para votar. Contestar como... Cancelar Rushikesh S Thakkar David Truong Hace 12 años @David,I agree with you on that. I too wouldn't like to run 2 different servers. We can use comet libraries for Java - like Grizzly (http://grizzly.java.net/), but websocket support is not yet available in IE and webkit (AFAIK). That's where socket.io comes to rescue.Moreover, Node.js is fares well on high load (plus: has good support for no-sql dbs like MongoD. So I wouldn't mind considering it as a backend for a Liferay app that renders realtime data. Por favor identifíquese para votar. Contestar como... Cancelar
Rushikesh S Thakkar David Truong Hace 12 años @David,I agree with you on that. I too wouldn't like to run 2 different servers. We can use comet libraries for Java - like Grizzly (http://grizzly.java.net/), but websocket support is not yet available in IE and webkit (AFAIK). That's where socket.io comes to rescue.Moreover, Node.js is fares well on high load (plus: has good support for no-sql dbs like MongoD. So I wouldn't mind considering it as a backend for a Liferay app that renders realtime data. Por favor identifíquese para votar. Contestar como... Cancelar
Koen De Jaeger Hace 11 años Some changes I had to make in the code in order to try the example.Change "local.host" to "localhost".Change "styles.css" to style.css". Por favor identifíquese para votar. Contestar como... Cancelar