Just released: A goog.BrowserChannel Server

[David Turnbull]

I am pleased to announce the immediate availability of an Apache-licensed server for the goog.BrowserChannel version 8 protocol.

https://github.com/dturnbull/browserchannel

Rejoice!

[Hochhaus, Andrew]

Excellent, thanks! :)

[David Turnbull]

Did you make good progress with your libevent implementation?  I see your google code project but there's only a wiki on there.

I just added better directions to the readme.  Please do comment if you try it out.

https://github.com/dturnbull/browserchannel

-david

[Hochhaus, Andrew]

On Fri, Aug 5, 2011 at 6:29 PM, David Turnbull <dtur...@gmail.com> wrote:
> Did you make good progress with your libevent implementation?  I see your
> google code project but there's only a wiki on there.

Yes, libevent-browserchannel-server is still under development. It
needs a bit more work before it is ready to release but I plan to do
the initial code checkin soon.

-Andy

[Ivan Kozik]

On Mon, Aug 8, 2011 at 14:59, Hochhaus, Andrew <ahoc...@samegoal.com> wrote:
> Yes, libevent-browserchannel-server is still under development. It
> needs a bit more work before it is ready to release but I plan to do
> the initial code checkin soon.
>
> -Andy

FWIW, I have a complete BrowserChannel replacement at
http://ludios.org/minerva/ that is *almost* ready for announcement.
The server-side code is Python/Twisted. I won't say too much right
now because it's not documented yet.

(Happy to see BrowserChannel servers, though.)

Ivan

[David Turnbull]

Awesome Ivan and Andy!  I updated the wiki so folks not searching this list can find this good stuff.

http://code.google.com/p/closure-library/wiki/ClosureLibraryResources

-david

[jos...@gmail.com]

Nice!

Since yesterday I've been working on a little browserchannel server implementation for nodejs:

https://github.com/josephg/node-browserchannel/

Its super buggy, but I have arrays & maps going back and forth to my browser.

I've got a few questions:

I've noticed that the google browserchannel server is now adding a whole bunch of junk text after the first payload in html-based backchannel. Why is that? Is it needed to force IE to parse the tags or something?

Also, why does the forward channel use query parameters? Wouldn't it be way easier &/ more powerful to send a JSON blob each time?

Cheers

Joseph

[Jacky]

The junk stuff are needed by IE, unfortunately. :(

And you may like refer to the following article for more info:
http://www.shanison.com/2010/05/10/stop-the-browser-%E2%80%9Cthrobber-of-doom%E2%80%9D-while-loading-comet-forever-iframe/

Best,
J

[Joseph Gentle]

Ah cool, thanks!

-J

[jos...@gmail.com]

My nodejs browserchannel server is ready to be used.

https://github.com/josephg/node-browserchannel/

Enjoy

-J