incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Hegarty <heg...@gmail.com>
Subject Re: Proxy issues
Date Thu, 27 Sep 2012 15:17:32 GMT
Hey Ali,
I'm in the process of trying to set this up, is there any chance of seeing
how the ssl cert and ports configuration that you used from the
server.config file?
Regards
hegsie

On Tue, Sep 25, 2012 at 10:33 AM, Ali Lown <a.lown0@gmail.com> wrote:

> Comet isn't really an option.
>
> The socket.io code is still in the codebase, but if the browser is
> detected
> to have a websocket implementation they will be used instead.
>
> I was hoping to be able to remove the socket.io code soon since all major
> browsers now support websockets (ignoring IE<10).
>
> If you only care about it working for your own server, you can compile it
> with native websockets disabled using the patch here:
>
> https://github.com/alown/wave/commit/7b81a846263a89869ff853a051ef381ad4da02e2
> You may also need the forced disabled socket.io patch here:
>
> https://github.com/alown/wave/commit/1bbc3db4449e92617cf1cf1c05c26144c4ee164a
> On 25 Sep 2012 10:21, "Ben Hegarty" <hegsie@gmail.com> wrote:
>
> > Yep same as wave, firefox continually tries to authenticate and chrome
> just
> > dies straight away, not that I know what it is but could we fall back to
> > comet (because it seems to be ok) for situations like these? :(
> >
> > Bugger really wanted to be able to use wave, thanks again for all your
> help
> > Ali, you're a star.
> > Regards
> > hegsie
> >
> > On Tue, Sep 25, 2012 at 10:15 AM, Ali Lown <a.lown0@gmail.com> wrote:
> >
> > > authenticate
> >
>



-- 
Mobile Phone: +447767-322-122
Work Phone: +4420 79485612

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message