On Sun, Jun 5, 2011 at 10:16 AM, Tom <tommed...@gmail.com> wrote:
> You're right, I've got it pretty much covered now. The answer was not to
> request the file ;)

> On a side note, could you maybe give my pull request a look?

> Thanks a lot.

> Tom

> 2011/6/5 Eric Zhang <e...@nowjs.com>

>> Hey Tom,

>> Socket.io is hosted by the socket.io library itself and not NowJS so
>> autoHost: false won't disable.

>> However NowJS will allow you to pass options through to socket.io , but
>> there doesn't appear to be a socket.io option to disable file hosting in
>> the latest 0.6

>> 3rdEden may have more insight about that.

>> Eric

>> On Sun, Jun 5, 2011 at 1:38 AM, Tom <tommed...@gmail.com> wrote:

>>> One more related question I have is, when setting autoHost to false,
>>> should I also host socket.io myself? If not, how can I disable now.js's
>>> hosting of socket.io?

>>> I need to host all these client side libraries myself, as I have more
>>> than 10 independent client-side modules now, so I need to merge, minify and
>>> gzip these to speed up my application's load time as much as possible.

>>> Tom

>>> 2011/6/3 Vladimir Dronnikov <dronni...@gmail.com>

>>>> > From a conceptual point of view it would make more sense to me to
>>>> define the
>>>> > server's address within the client-side file (and not on the server
>>>> side).

>>>> IMHO, this is right. This would 1) allow to have multiple now.js
>>>> instances on the page; 2) fine grain security options; 3) draw
>>>> unobvious preparation of the file for vanilla static servers.

>>>> Best regards,
>>>> --Vladimir