> I'm pleased to announce the release of Orbited 0.6.0. With this release,
> Orbited has officially moved from alpha status to beta. At this point
> Orbited is stable enough to be used in production environments. While we
> will be adding new features, we have no plans to change the core
> functionality or APIs. Note that Orbited 0.6.0 does not support the
> deprecated Orbit dispatch protocol. Orbited 0.6.0 can be downloaded from the
> Cheeseshop (http://pypi.python.org/pypi/orbited), or with easy_install -U
> orbited

> Thanks to everyone who contributed to this release:

> Mario Balibrera
> Michael Carter
> Marcus Cavanaugh
> Petar Dobrev
> Jonathan Ellis
> Paul Jones
> Rui Lopes
> Jacob Rus
> Frank Salim
> Adrian Weisberg
> And more...

> Note some of the changes:

> New API:
>    - Include /static/Orbited.js which provides Orbited.TCPSocket
>    - The TCPSocket constructor takes no arguments. TCPSocket.open takes
> hostname and port. (and optional isBinary)
>    - Binary mode no longer returns integer Arrays -- it returns strings.
> These strings contain all of the binary data that the arrays used to.

> Correct handling of close and onclose
>    - When the remote connection closes, you will get an onclose callback
>    - When contact with Orbited is interrupted, after a configurable timeout,
> onclose will be called
>    - A call to  TCPSocket.close, will immediately close the remote
> connection
>    - A call to TCPSocket.reset will immediately clean up the browser
> connection, and attempt to immediately close the connection between the
> remote server
>    (reset should be used in conjunction with ununload)

> Far more stable browser code:
>     - Opera now works cross-subdomain
>     - Transport-level auto reconnect with incremental backoff
>     - Configurable timeout (increase for use over intermittent networks)
>     - Eliminated javascript instability due to page navigations and memory
> overuse

> New transports
>     Polling and Long Polling added
>     These can optionally be used in cases where reverse proxies buffer
> streaming requests

> And more...

> -Michael Carter

> We aren't targeting framework integration at the moment, but over the next
> couple of releases I'm sure we'll have some tutorials again. If you are
> interested in building an application with RoR and Orbited, and writing a
> tutorial, feel free to talk with us in #orbited on freenode -- we'll answer
> whatever questions you have.

> -Michael Carter

> On Fri, Aug 15, 2008 at 5:24 PM, yskhoo <ysk...@gmail.com> wrote:

> > Will there be a RoR tutorial to go with the new version of Orbited
> > anytime soon?

> > On Aug 13, 10:20 am, "Michael Carter" <cartermich...@gmail.com> wrote:
> > > I'm pleased to announce the release of Orbited 0.6.0. With this release,
> > > Orbited has officially moved from alpha status to beta. At this point
> > > Orbited is stable enough to be used in production environments. While we
> > > will be adding new features, we have no plans to change the core
> > > functionality or APIs. Note that Orbited 0.6.0 does not support the
> > > deprecated Orbit dispatch protocol. Orbited 0.6.0 can be downloaded from
> > the
> > > Cheeseshop (http://pypi.python.org/pypi/orbited), or with easy_install
> > -U
> > > orbited

> > > Thanks to everyone who contributed to this release:

> > > Mario Balibrera
> > > Michael Carter
> > > Marcus Cavanaugh
> > > Petar Dobrev
> > > Jonathan Ellis
> > > Paul Jones
> > > Rui Lopes
> > > Jacob Rus
> > > Frank Salim
> > > Adrian Weisberg
> > > And more...

> > > Note some of the changes:

> > > New API:
> > >    - Include /static/Orbited.js which provides Orbited.TCPSocket
> > >    - The TCPSocket constructor takes no arguments. TCPSocket.open takes
> > > hostname and port. (and optional isBinary)
> > >    - Binary mode no longer returns integer Arrays -- it returns strings.
> > > These strings contain all of the binary data that the arrays used to.

> > > Correct handling of close and onclose
> > >    - When the remote connection closes, you will get an onclose callback
> > >    - When contact with Orbited is interrupted, after a configurable
> > timeout,
> > > onclose will be called
> > >    - A call to  TCPSocket.close, will immediately close the remote
> > > connection
> > >    - A call to TCPSocket.reset will immediately clean up the browser
> > > connection, and attempt to immediately close the connection between the
> > > remote server
> > >    (reset should be used in conjunction with ununload)

> > > Far more stable browser code:
> > >     - Opera now works cross-subdomain
> > >     - Transport-level auto reconnect with incremental backoff
> > >     - Configurable timeout (increase for use over intermittent networks)
> > >     - Eliminated javascript instability due to page navigations and
> > memory
> > > overuse

> > > New transports
> > >     Polling and Long Polling added
> > >     These can optionally be used in cases where reverse proxies buffer
> > > streaming requests

> > > And more...

> > > -Michael Carter

yskhoo wrote:
> Oh that would actually be awesome!
> How do I find #orbited on freenode?

Ben Weiner wrote:
> features, it looks as though it has been necessary to change it to the
> extent that it breaks the documentation and examples on
> http://www.orbited.org/.

Ben Weiner wrote:
> Ben Weiner wrote:

>> features, it looks as though it has been necessary to change it to the
>> extent that it breaks the documentation and examples on
>> http://www.orbited.org/.

> Just to give an example:
> http://www.orbited.org/wiki/TCPSocket has a section: "Using TCPSocket in
> Orbited 0.5". This is all now incorrect as adding

> <script src="http://yourdomain:8000/static/TCPSocket.js"></script>

> to a page will result in a 404.

> :(

Rui Lopes wrote:
> As Michael described in the announce email, a few incompatible changes
> were introduced:

> """
> New API:
>    - Include /static/Orbited.js which provides Orbited.TCPSocket
>    - The TCPSocket constructor takes no arguments. TCPSocket.open takes
> hostname and port. (and optional isBinary)

> To see how this works, have a look at the bundled demos; eg, see the
> telnet demo at:

>   http://js.io/trac/browser/trunk/protocols/telnet/telnet.js
>   http://js.io/trac/browser/trunk/demos/telnet/index.html
>   http://js.io/trac/browser/trunk/demos/telnet/telnet-gui.js

Ben Weiner wrote:

>> To see how this works, have a look at the bundled demos; eg, see the
>> telnet demo at:

>>   http://js.io/trac/browser/trunk/protocols/telnet/telnet.js
>>   http://js.io/trac/browser/trunk/demos/telnet/index.html
>>   http://js.io/trac/browser/trunk/demos/telnet/telnet-gui.js

> OK, thank you.

> I have to say, I do need my hand holding on configuration as I have not
> read the python source code. I have, of necessity, read a lot of the
> Orbited.js file...

Rui Lopes wrote:
> The configuration is described at:
>>   http://orbited.org/wiki/Configuration

>> But there were a few changes with 0.6, one of them was the syntax on the
>> "[access]" zone;  for making the telnet example work, you'll need to
>> change orbited.cfg by adding "* -> www.google.com:80" into the
>> "[access]" zone, eg:

>> [access]
>> * -> www.google.com:80

>> This reads as, let any client connect to www.google.com at port 80.

I wrote:
> And (changing the subject ;-) can I do

> conn = new Orbited.TCPSocket();

> and then
> conn.open('host1','8000');

Ben Weiner wrote:
> Hi Rui,

> Rui Lopes wrote:

>> The configuration is described at:

>>>   http://orbited.org/wiki/Configuration

>>> But there were a few changes with 0.6, one of them was the syntax on the
>>> "[access]" zone;  for making the telnet example work, you'll need to
>>> change orbited.cfg by adding "* -> www.google.com:80" into the
>>> "[access]" zone, eg:

>>> [access]
>>> * -> www.google.com:80

>>> This reads as, let any client connect to www.google.com at port 80.

> Thanks: I'd just about started to approach a similar understanding by
> reading the changesets ;-\

> So, can I do:

> host1:8000 -> google.com:80
> host1:8000 -> google.com:81

> Or is that illegal?

> And (changing the subject ;-) can I do

> conn = new Orbited.TCPSocket();

> and then
> conn.open('host1','8000');

> if I want to make straight TCP connections rather than stomp, telnet,
> chat, etc? Calling TCPSocket() with arguments, that worked /very/
> sweetly in 0.5...

Rui Lopes wrote:
> Just use an "*" in the left hand side (LHS) to match any client IP
> address, or use a specific IP address.  I'm not sure if it lets you
> define the port number, but in the normal case, it does not make sense,
> because you cannot control which port the browser uses to access orbited.

> The right hand side is the destination hostname:port (arguments passed
> into the TCPSocket.open function) to which the client is allowed to open
> the socket.

Excellent.

> Use it like (as you can see on telnet.js):

> conn = new Orbited.TCPSocket();
> // set the callbacks here, eg: conn.onopen = function{ alert("socket is open"); };
> conn.open('google.com', 80);

Michael Carter wrote:
> On Thu, Aug 21, 2008 at 4:17 AM, Ben Weiner <b...@readingtype.org.uk
> <mailto:b...@readingtype.org.uk>> wrote:

>     Hi,

>     Rui Lopes wrote:
>     > Just use an "*" in the left hand side (LHS) to match any client IP
>     > address, or use a specific IP address.  I'm not sure if it lets you
>     > define the port number, but in the normal case, it does not make
>     sense,
>     > because you cannot control which port the browser uses to access
>     orbited.

>     Well you can specify it, but whether you *want* to ... ;-)

>     I found that in Orbited 0.5 I was able to specify the port number when
>     calling the TCPSocket.js script from /static, but with 0.6 the
>     call that
>     the script makes to /tcp (gets a session ID?) did not have the port
>     number included. That caused me some considerable confusion but in the
>     end I mod-rewrite proxied the Orbited server, which is running
>     alongside
>     Apache. Sledgehammer? It seemed to do the trick.

> You can control which port the browser uses to access Orbited.

> Orbited.settings.port = 8001;

> While the proxying may work, its not going to be your most scalable bet.

Rui Lopes wrote:
> Michael Carter wrote:

<snipped>
>> You can control which port the browser uses to access Orbited.

>> Orbited.settings.port = 8001;

>> While the proxying may work, its not going to be your most scalable bet.

> Is that setting is for defining the destination port where orbited
> listens, that is, the port where orbited is listening?

> What is its relation to the port we define in left hand side on the
> "[access]" configuration?

> Eg: what is the meaning of the following configuration?

> [access]
> *:12345 -> localhost:7

> As a note, in my original answer, I was talking about the source port
> the browser uses to connect to orbited, not the port where orbited is
> listening.

> > Is that setting is for defining the destination port where orbited
> > listens, that is, the port where orbited is listening?

> > What is its relation to the port we define in left hand side on the
> > "[access]" configuration?

> > Eg: what is the meaning of the following configuration?

> > [access]
> > *:12345 -> localhost:7

> > As a note, in my original answer, I was talking about the source port
> > the browser uses to connect to orbited, not the port where orbited is
> > listening.

> So to summarise the conversation, it looks to me like port configuration
> is like this:

> -  Browser outgoing: undefined (and cannot be defined)
> -  Orbited incoming (the connection over http):
>   -  defined for the browser with Orbited.settings.port and
>   -  for the Orbited server on the left-hand side of an access directive.
> -  Orbited outgoing (the connection to the persistent network service,
> eg TCP): defined on the right-hand side of an access directive.

> Therefore you need to set ports in:
> Orbited.js
> orbited.cfg