OSSLine: Aggregated RSS/Atom Feeds of Everything OSSLine

tag 3.2 and google compiler broken

ossline — Fri, 03 Sep 2010 19:33:27 +0000

closure compiler minifying jsio/util/browser.js
Failed compiling jsio/util/browser.js
stdin:1: ERROR - Parse error. invalid return
if (jsio.__env.name != 'browser') { return; }
^
1 error(s), 0 warning(s)
make: *** [all] Error 1

Re: Problems with Orbited.js: ERROR LOADING jsio/net/protocols/mspp.js : TypeError: Object # has no method ‘getLogger’

ossline — Fri, 27 Aug 2010 20:10:18 +0000

I think the js.io apis changes from jsio.logging.getLogger to
jsio.logging.get()

More importantly, loggers are in each scope by default, so you can
probably just delete whatever offending getLogger line is there.

Also, you should do any compilations against the 3.2 tag of js.io --
things are changing rapidly in trunk.

Re: [Orbited] Re: Announcing Orbited2 Beta

ossline — Fri, 27 Aug 2010 19:33:13 +0000

On Fri, Aug 27, 2010 at 12:17 PM, Erik Anderson <
Orbited2 supports the same use case that Orbited supports -- a tcp proxy.
Orbited2 is an architectural drop-in replacement for Orbited.
Orbited2 has two basic modes
1) Exposing a WebSocket api to the browser, and sending WebSocket data (with
the WS protocol) to a back-end server.

Re: Announcing Orbited2 Beta

ossline — Fri, 27 Aug 2010 19:17:07 +0000

Trying to wrap my head around this... I think my use case is still
that of using TCPSockets, in which case WebSockets becomes an
infinitely more efficient transport protocol, but the daemon still
maintains its purpose as a transport proxy, at least when you're
dealing with a service that doesn't speak native WebSocket (or

Re: Not killing proxied connection when browser leaves page

ossline — Thu, 26 Aug 2010 15:05:57 +0000

It's getting called the first time by CometTransport's close method,
in base.py. But that gets called after every write. Shouldn't
connectionLost be called only when the client disconnects?

Here's the stack trace from pdb:
(Pdb) w
/usr/local/bin/orbited(8)<modu le>()
-> load_entry_point('orbited==0.7 .10', 'console_scripts', 'orbited')()

Re: Not killing proxied connection when browser leaves page

ossline — Thu, 26 Aug 2010 14:21:35 +0000

I've seen this as well (i.e IRC closing by timeout and Orbited not
closing). I think this is to due with the issues with the CSP protocol
not closing properly (also causing the issues on
[link])

mcarter, I know your busy, but can you check

Re: [Orbited] Not killing proxied connection when browser leaves page

ossline — Thu, 26 Aug 2010 03:52:59 +0000

Not sure if that is quite right... if you look at TCPResource.render (this
is what gets called each time a client attempts to handshake) you see where
an instance of a TCPConnectionResource is created. There should always be
one of these created per connection.
Perhaps the lostTriggered is being set improperly elsewhere. I would think

Not killing proxied connection when browser leaves page

ossline — Thu, 26 Aug 2010 03:37:32 +0000

I'm having trouble getting orbited to kill the connection it's
proxying.

I'm using it to run IRC through a web browser. When the user
disconnects, I would expect the IRC server to show the "remote host
closed the connection" message, but instead I get ping timeout. So
the code in proxy.py (in connectionLost) isn't killing the connection.

Re: [Orbited] Re: Announcing Orbited2 Beta

ossline — Wed, 25 Aug 2010 22:55:54 +0000

Sounds about right. If tornado is a websocket server, then just use
Orbited2.js to put a websocket in IE, etc. and you're good to go.
- Michael Carter

Re: Announcing Orbited2 Beta

ossline — Wed, 25 Aug 2010 22:13:27 +0000

So for instance I could do the following with Orbited2:

Deploy Orbited2, and use the Javascript library Orbited2.js and use
Websockets in any browser (including IE?).
Write a Tornado websocket server, which could deal with authentication
from the incoming request.
Once authenticated my Tornado setup could subscribe to a AMQP message