martynsmith/pocketio — comment on commit 577b0fb301c488bbe5e51fd624eacc63e79b11cd
File:  line 0
By martynsmith:

It's mostly just for convenience (to save effort). Failing that, I might
just subclass the poll object myself.

I also added room support, I did this by adding join/leave methods to the
Socket, Connection, and Pool objects, then also adding a room_send method
to the Pool object.

Ideally I'd like to push this upstream too, does it sound like something
you'd be open to?

and why specifically don't you want to add emit() to the Pool object?

On Sat, Feb 11, 2012 at 8:21 PM, Viacheslav Tykhanovskyi <
reply@reply.github.com
> wrote:

> I am not very sure about adding emit method to the pool...
>
> But you can always achieve that by passing already built message, for
> example:
>
> my $event = PocketIO::Message->new(type => 'event', data => {name =>
> 'my_event', args => [1, 2, 3]});
> $pool->send($event);
>
> This will send an 'event message' to everybody in the pool.
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/martynsmith/pocketio/commit/577b0fb301c488bbe5e51fd624eacc63e79b11cd#commitcomment-956217
>