On Wed, Apr 11, 2012 at 11:16 AM, Alan Hoffmeister <
alanhoffmeis...@gmail.com> wrote:
> Yep I could use it, but keep a persistent connection for every visitor
> will consume a lot more resources from the server then a restfull service.
a) That's why you're using Node - it copes with massive con
You can't get the callback functionality without
1. Long polling
2. WebSockets
You need to do one on the two if you want the server to call back the
client.
NowJs or DNode is what I would recommend
Sent from my Windows Phone
--
From: Alan Hoffmeister
Sent: 4/11/2012
What Alan is describing could be done with just http - the client is
sending a message that the server responds to.
Socket.io etc is great when you want to send data from the server to the
client, but that's not what Alan describes.
With that being said, I don't know any module that have the funct
Well, I'm implementing one endpoint that can handle RPC-like requestest,
I'll up that package to npm when finished :)
--
Att,
Alan Hoffmeister
2012/5/31 David Björklund
> What Alan is describing could be done with just http - the client is
> sending a message that the server responds to.
> Soc
I wish I could say: "Let's rock'n websockets!", but I had bad experiences
using socket.io behind firewalls.. That's why I'm fallbacking to RPC...
--
Att,
Alan Hoffmeister
2012/5/31 tjholowaychuk
> raw socket.io is more than enough IMHO
>
> On Apr 11, 7:58 am, Alan Hoffmeister
> wrote:
> > I w
Socket.io 1.0 is going to directly address that limitation. Instead of
trying to establish the best possible connection first, it will start
with the most reliable connection and upgrade to websockets if it can.
Daniel Shaw
@dshaw
On Thu, May 31, 2012 at 11:33 AM, Alan Hoffmeister
wrote:
> I wi
@Alexey, this is what I'm doing ;)
@Dan Shaw I hope so, it would be much more easy and secure for production.
--
Att,
Alan Hoffmeister
2012/5/31 Alexey Petrushin
> > What Alan is describing could be done with just http
> Yes, I believe You are right, it doesn't require socked support and can b
