Re: [nodejs] Socket.io client alternative

2015-05-04 Thread Guillermo Rauch 
Starting with 1.5 we'll remove most of the legacy browser support, in a way
that compatibility can still be retained through polyfilling. That said,
client code build size is probably one of the last things you should be
optimizing. By the time the code loads, gets parsed and the socket
connects, the user could already be looking at data

.

—
@rauchg 

On Mon, May 4, 2015 at 8:12 AM klrumpf  wrote:

>  https://github.com/faye/faye-websocket-node
>
> works very nicely
>
>
>  
> On 03/05/15 04:07, Kevin Ingwersen (Ingwie Phoenix) wrote:
>
> Hey.
>
> Have you noticed, that - uncompressed - socket.io-client is pretty huge, 
> actually? It almost competes with jQuery. That is why I would like to know if 
> there is a thinner alternative to the „original“ client?
>
> Kind regards, Ingwie.
>
>
>
>  --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/55471FCF.4090302%40gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAHsm-idPVWdrHDWAvf_dXkz1Tky72z1aFUDxTi7%2BcdFbvoAUuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Socket.io, express and sticky sessions. How to...

2015-04-16 Thread Guillermo Rauch 
Check out:
http://socket.io/docs/using-multiple-nodes/#sticky-load-balancing

for up-to-date information on the topic.

—
@rauchg 

On Thu, Apr 16, 2015 at 6:15 AM Kevin Ingwersen (Ingwie Phoenix) <
ingwie2...@googlemail.com> wrote:

> Hey everyone.
>
> If you peered into the list, you may saw that I was asking for help ins
> caling my app. And I got that one working just as I wanted; using
> „various-cluster“ for a pretty neat way to spawn multiple workers of
> specific scripts. That one is pretty neat. I use a Frontent-Worker that
> only does what it osund slike; managing stuff for the frontend, my HTTP
> server, for instance. However… socket.io requires ~3 requests for a
> handshake. I am assuming that the first is to get a session, the second is
> to negotiate a transport and the third is to actually „connect“.
>
> But if request 1 and 2 are handled on different servers, socket.io fails
> in it’s error handling for good. Although the server sends back a crisp
> clear error message, socket.io attempts to re-connect instead of letting
> a developer know of the mandatory issue.
>
> So, I went to read. Socket.io recommends http://npmjs.com/sticky-session …
> boy is that thing outdated, at least it feels that way. It had no example
> for Express, and my guts told me that if it had one, it would be for
> Express 3 instead of 4, which I use.
>
> Further research brought up the issue #7, which refers to Express not
> behaving with sticky-session … cool, really. I totally jumped in joy. :(
> To make things worse; it’s not resolved. I tested it and it didn’t work.
>
> Does any one of you know of a way to enable sticky sessions *when already
> being in a worker*? various-cluster already spawns my frontent_worker.js
> in a worker process, so cluster.isMaster should be false in any case…at
> least I’d think so.
>
> So if anyone has an idea for this, then please let me know. Thanks!
>
> Kind regards,
> Ingwie
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/8DEF5947-1620-4F5D-804B-301D249AE34F%40googlemail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAHsm-icnKf7iX-TykRNrU1WiNVXgP%3D2ZewYKwHQ0Og%2BnQViPWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] socket.io on clusters: broadcasting to all sockets...

2015-04-11 Thread Guillermo Rauch 
Check this out:
http://socket.io/docs/using-multiple-nodes/#passing-events-between-nodes

—
@rauchg 

On Sat, Apr 11, 2015 at 10:36 AM Kevin Ingwersen (Ingwie Phoenix) <
ingwie2...@googlemail.com> wrote:

> Hey.
>
> So now that I have a plan for scaling my Express app, I am likely going to
> give my Socket.io service the same treat. But there is a little bit of a
> concern I have.
>
> Say I have 2 workers for a chat service. A good way to promote that a user
> logged in is to broadcast to all sockets connected…but how exactly will
> this work if worker#1 sends the broadcast - will worker#2’s sockets also be
> affected? I dont know if cluster.fork()’ed processes share the sockets or
> not…
>
> Kind regards,
> Ingwie
>
> --
> Job board: http://jobs.nodejs.org/
> New group rules:
> https://gist.github.com/othiym23/9886289#file-moderation-policy-md
> Old group rules:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> To post to this group, send email to nodejs@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/nodejs/08C9570E-EE51-4F86-AF8E-E39A171760BA%40googlemail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Job board: http://jobs.nodejs.org/
New group rules: 
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/nodejs/CAHsm-idUx6N5qnPzZuY8e0-6CtD1x9YgZo5jaNFrnGzeM%3D5peQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [nodejs] Node.js & Socket.IO simply do not work.

2014-01-19 Thread Guillermo Rauch 
You're listening on the `server` object.


>1. server.on('my other event', function (data) {
>
>
You should be listening on the `client` object in your server code. The
events are emitted per-socket.


On Sun, Jan 19, 2014 at 12:00 PM, FirstName LastName
wrote:

> Server sends message just fine; the client will receive the message. BUT
> NO MATTER WHAT I TRY, THE CLIENT WILL NOT SEND A MESSAGE TO THE SERVER.
>
> server
>
> http://pastebin.com/KsQrSY7t
>
> client
>
> http://pastebin.com/0g9CziuW
>
> Why can't the client send a message to the server?!
>
> I have tested this on two different environments. Same issue.
>
> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Guillermo Rauch
Cloudup CTO
http://devthought.com

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Compressing requests (gzip?)

2013-07-05 Thread Guillermo Rauch 
POST compression is indeed not supported, which would make compression
unidirectional for the polling transport.


On Fri, Jul 5, 2013 at 1:00 PM, Ryan Schmidt wrote:

>
> On Jul 5, 2013, at 01:36, Arnout Kazemier wrote:
>
> > What makes you think there's no standard for compression?
>
> Because I Googled "socket.io compression" and found pages like this:
>
>
> This unresolved socket.io issue requests per-frame deflate support be
> added:
>
> https://github.com/LearnBoost/socket.io/issues/1148
>
>
> This discussion says socket.io doesn't use compression, and suggests an
> in-browser JavaScript-based compression method:
>
> https://groups.google.com/forum/#!topic/socket_io/zU5BE8vhMnY
>
> It references this page:
>
> http://www.mail-archive.com/whatwg@lists.whatwg.org/msg20418.html
>
> Which says:
>
> > The current Web Socket wire protocol does not make allowances for
> compression.
>
>
> Although that is from 2010.
>
>
> This page talks about optimizing websocket traffic by making JSON data
> smaller, for example using an ordered array instead of an object with named
> keys.
>
> http://buildnewgames.com/optimizing-websockets-bandwidth/
>
> At the end, it explains why true compression is not possible:
>
> > Older drafts of the WebSocket specification described a deflate-stream
> extension that applied compression to the stream. However, there were many
> potential issues with this extension. Len Holgate sums up the pitfalls
> regarding deflate-stream, which was pulled in 11th draft of the
> specification (§9.2.1). There is an alternative, however, and that is
> theper-frame DEFLATE extension.
> >
> > The good news is that the deflate-frame extension landed in WebKit back
> in February. The bad news is that there is not yet a WebSocket
> implementation in node.js that implements the extension, although that will
> hopefully change really soon.
>
>
> "that will hopefully change really soon" is a link to an unresolved issue
> in the ws bug tracker:
>
> https://github.com/einaros/ws/issues/34
>
>
> > WebSockets have a deflate extensions
>
> According to what I've read, there used to be per-stream deflate support,
> it was removed because it was problematic, they were talking about adding
> per-frame deflate support, and lately have changed this to proposing
> per-message deflate support, but I don't know if this spec was finalized or
> if any browsers implement it.
>
>
> > and gzip is support by nearly every browser that you can download.
>
> For normal HTTP responses, I have no doubt of this. For POST requests, I'm
> having trouble finding confirmation of that. For web sockets, the
> information I'm finding says this is not the case at this time, but the
> reason I'm asking is I'm not sure how current the information is that I
> found.
>
>
>
> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>


-- 
Guillermo Rauch
Cloudup CTO
http://devthought.com

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [nodejs] Socket.io error

2013-01-22 Thread Guillermo Rauch 
This is harmless. It occurs with certain proxies that break the websocket
protocol, and can't really be avoided. The client will just fall back to
xhr-polling.


On Tue, Jan 22, 2013 at 5:52 PM,  wrote:

> Hello, i made a medium size app, the server was running for 2 days(with
> some tests and no hard work) and then i started to use it on the company
> that requested it, but after 4 hours of work(several request from 4
> different machines), the following error pops up:
>
> warn: websocket parser error: continuation frame cannot follow current
> opcode
>
>
> i have no clue why, some stuff still works, i dont know where is the
> error, it doesn't make any sense, 1 event no error, on another event the
> error happens, i triggered the same event with the same data on another
> machine it worked, but on the one connected for 4 hours it crashed, but its
> odd because other events worked while that one failed, any clue why?
> i guess i messed up my explanation, but you get the idea(i hope) =p
>
> thanks you all for reading that bad English,
> bb
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>



-- 
Guillermo Rauch
LearnBoost CTO
http://devthought.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Best practice for SSL termination with Socket.io

2012-08-13 Thread Guillermo Rauch 
No. Stud can use the PROXY protocol to communicate with HAProxy. From the
README:

stud will optionally write the client IP address as the first few octets
> (depending on IPv4 or IPv6) to the backend--or provide that information
> using HAProxy's PROXY protocol.


-- 
Guillermo Rauch
LearnBoost CTO
http://devthought.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Best practice for SSL termination with Socket.io

2012-08-10 Thread Guillermo Rauch 
That's what I was clarifying. In reality it doesn't really *support* the
WebSocket *protocol*, and that's why it can't add the X-Forwarded-For.
It supports it in the same way it supports _any other_ protocol in TCP mode
(like XMPP), just forward the traffic along.

-- 
Guillermo Rauch
LearnBoost CTO
http://devthought.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Best practice for SSL termination with Socket.io

2012-08-10 Thread Guillermo Rauch 
Until ELB adds WebSocket support.

-- 
Guillermo Rauch
LearnBoost CTO
http://devthought.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Any Engine.IO news?

2012-08-10 Thread Guillermo Rauch 
Indeed!

On Fri, Aug 10, 2012 at 10:21 AM, Arunoda Susiripala <
arunoda.susirip...@gmail.com> wrote:

> So that means socket.io 1.0 comes with inbuilt engine.io.
>
> Cool. Great stuff.
>
>
> On Fri, Aug 10, 2012 at 10:49 PM, Guillermo Rauch wrote:
>
>> There's about 4 blocking tickets for Socket.IO 1.0:
>>
>> https://github.com/LearnBoost/engine.io/issues?direction=desc&sort=created&state=open
>>
>> At the moment it's looking really stable, but we need a few extra
>> features in place.
>>
>> On Fri, Aug 10, 2012 at 4:13 AM, Arunoda Susiripala <
>> arunoda.susirip...@gmail.com> wrote:
>>
>>> It quite while we have heard about Engine.IO.
>>> And it was mentioned that it's future roadmap along with Socket.IO will
>>> be announced soon.
>>>
>>> So I just need to know, how about the status of Engine.IO now?
>>>
>>> --
>>> Arunoda Susiripala
>>>
>>> @arunoda <http://twitter.com/arunoda>
>>> <http://gplus.to/arunoda>https://github.com/arunoda
>>> http://www.linkedin.com/in/arunoda
>>>
>>>  --
>>> Job Board: http://jobs.nodejs.org/
>>> Posting guidelines:
>>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to nodejs@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> nodejs+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>>
>>
>>
>>
>> --
>> Guillermo Rauch
>> LearnBoost CTO
>> http://devthought.com
>>
>>  --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>
>
>
> --
> Arunoda Susiripala
>
> @arunoda <http://twitter.com/arunoda>
> <http://gplus.to/arunoda>https://github.com/arunoda
> http://www.linkedin.com/in/arunoda
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>



-- 
Guillermo Rauch
LearnBoost CTO
http://devthought.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Any Engine.IO news?

2012-08-10 Thread Guillermo Rauch 
There's about 4 blocking tickets for Socket.IO 1.0:
https://github.com/LearnBoost/engine.io/issues?direction=desc&sort=created&state=open

At the moment it's looking really stable, but we need a few extra features
in place.

On Fri, Aug 10, 2012 at 4:13 AM, Arunoda Susiripala <
arunoda.susirip...@gmail.com> wrote:

> It quite while we have heard about Engine.IO.
> And it was mentioned that it's future roadmap along with Socket.IO will be
> announced soon.
>
> So I just need to know, how about the status of Engine.IO now?
>
> --
> Arunoda Susiripala
>
> @arunoda <http://twitter.com/arunoda>
> <http://gplus.to/arunoda>https://github.com/arunoda
> http://www.linkedin.com/in/arunoda
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>



-- 
Guillermo Rauch
LearnBoost CTO
http://devthought.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] cluster API is amazing

2012-06-17 Thread Guillermo Rauch 
Please check out the 'cluster' branch. I'm adding cluster support to 
socket.io's new realtime engine (github.com/learnboost/engine.io) 

-- 
Guillermo Rauch
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Sunday, June 17, 2012 at 1:08, Fadrizul H wrote:

> Yeah, clustering is awesome. But if you start using sockets or the module 
> socket.io (http://socket.io). then all hell breaks loose. >.<
> On Jun 17, 2012 2:39 AM, "Diogo Resende"  (mailto:drese...@thinkdigital.pt)> wrote:
> > I have a module to abstract this, called rack (node-rack on github). I have 
> > to check the changes (I know they are some) to work with version 0.8.
> > 
> > -- 
> > Diogo Resende
> > 
> > 
> > On Saturday, June 16, 2012 at 19:29 , carter-thaxton wrote:
> > 
> > > Sorry, Nuno.  The project itself is closed-source.
> > > 
> > > But it wasn't particularly tough to implement.  I basically just tweaked 
> > > the code examples from:
> > > http://nodemanual.org/latest/nodejs_ref_guide/cluster.html
> > > 
> > > One of the things that's cool about the cluster API is that the child 
> > > processes just create HTTP or TCP servers like they would have as a 
> > > standalone single-process server.  The only difference is a big if-stmt 
> > > at the top of your program that check if you're running as a master or a 
> > > worker, and if you're the master, fork off the workers.  The rest of my 
> > > server basically remained the same. 
> > > 
> > > Of course, once I got it working, I added some tweaks to my logging code, 
> > > to include the PID for the worker process in every log line, and that 
> > > sort of thing.
> > > 
> > > > 
> > > -- 
> > > Job Board: http://jobs.nodejs.org/
> > > Posting guidelines: 
> > > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> > > You received this message because you are subscribed to the Google
> > > Groups "nodejs" group.
> > > To post to this group, send email to nodejs@googlegroups.com 
> > > (mailto:nodejs@googlegroups.com)
> > > To unsubscribe from this group, send email to
> > > nodejs+unsubscr...@googlegroups.com 
> > > (mailto:nodejs+unsubscr...@googlegroups.com)
> > > For more options, visit this group at
> > > http://groups.google.com/group/nodejs?hl=en?hl=en
> > 
> > -- 
> > Job Board: http://jobs.nodejs.org/
> > Posting guidelines: 
> > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> > You received this message because you are subscribed to the Google
> > Groups "nodejs" group.
> > To post to this group, send email to nodejs@googlegroups.com 
> > (mailto:nodejs@googlegroups.com)
> > To unsubscribe from this group, send email to
> > nodejs+unsubscr...@googlegroups.com 
> > (mailto:nodejs%2bunsubscr...@googlegroups.com)
> > For more options, visit this group at
> > http://groups.google.com/group/nodejs?hl=en?hl=en
> -- 
> Job Board: http://jobs.nodejs.org/
> Posting guidelines: 
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] Re: updating my UI when my server got a message via socket.io

2012-04-22 Thread Guillermo Rauch 
Separating responsibilities between different apps is almost always a good
choice. Communicating those apps through messages (eg: ømq) leads to good
architecture.

-- 
Guillermo Rauch
LearnBoost CTO
http://devthought.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Re: [nodejs] [ANN] Protein

2012-04-12 Thread Guillermo Rauch 
Interesting post that might hint at __proto__ never going away:
https://mail.mozilla.org/pipermail/es-discuss/2011-December/019083.html

On Thu, Apr 12, 2012 at 4:34 PM, Mathias Buus  wrote:

> You are completely right. I see a lot of other modules mutating __proto__
> though like express and socket.io so hopefully v8 will continue to
> support it.
>
> On 12/04/2012, at 21.19, Tim Caswell  wrote:
>
> Cool.  Just be aware that __proto__ is both non standard and deprecated.
> I'm not sure how this would be done with pure ES5 or ES6 code though.  I
> really like how protein just returns a function and doesn't mess with the
> HttpServer or subclass it like connect does.
>
> On Thu, Apr 12, 2012 at 2:06 PM, Mathias Buus wrote:
>
>> Yes I am mutating the __proto__ link of the request and response.
>>
>> One question, how do you extend the prototypes once (not per request)
>> without changing the http prototypes.  Are you mutating the .__proto__ of
>> the request when it comes in from node?
>>
>>
>>  --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nodejs@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
>  --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nodejs@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>



-- 
Guillermo Rauch
LearnBoost CTO
http://devthought.com

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en