Need some help in understanding ORBITED functionality

[saurabh]

Hi All,
I am pretty new to ORBITED so please escuse me if my question is too
weired.
I am making it point wise to check if i had understood things
correctly

1. As far as I understood ORBITED enabled reverse ajax ie server push
that means the http connection
between Clinet and server is not released and data is sent on that
connection.

2. Now suppose I want to make a chat kind of application then Clients
will connected to server using simple http only ( however using
ORBITED javascript) and two clients can chat using some mesage queue.

3. The message queue used for communication is internal to the server
and clients dont need to know about them.

4. [ Most Imp ] So in any case I dont require a public IP if i am
launching a platform where people can chat.
All Communication between client and server will happen over http so
new need of public ip ( as dont need any listening port to listen to
client requests over sockets)

Actually I am using a shared hosting server ( bluehost ) and want to
know if I need to get a public ip to run the chat application.

Thanks
Saurabh

--
http://reviewpunch.com/
Rate and review Products ,Services,Movies,Hotels,Restaurants,Mobile
phones,Electronic equipment,Startups

http://groups.google.com/group/ramprastha-gurgaon/
( Group for actual/prospective buyers of Ramprastha Gurgaon View/
Atrium/Edge )

"Successful people make more mistakes because they do more "
Thanks
Saurabh Agarwal

[Jacob Rus]

saurabh wrote:
> I am making it point wise to check if i had understood things
> correctly
>
> 1. As far as I understood ORBITED enabled reverse ajax ie server push
> that means the http connection
> between Clinet and server is not released and data is sent on that
> connection.
>
> 2.  Now suppose I want to make a chat kind of application then Clients
> will connected to server using simple http only ( however using
> ORBITED javascript)  and two clients can chat using some mesage queue.
>
> 3. The message queue used for communication is internal to the server
> and clients dont need to know about them.

Yes, this is all correct.

> 4. [ Most Imp ] So in any case I dont require a public IP if i am
> launching a platform where people can chat.
> All Communication between client and server will happen over http so
> new need of public ip ( as dont need any listening port to listen to
> client requests over sockets)
>
> Actually I am using a shared hosting server ( bluehost ) and want to
> know if I need to get a public ip to run the chat application.

You need to run Orbited on some out-facing IP, of course, because
browsers must connect to it (or possibly have your HTTP server work as
a proxy in front of Orbited). Your back-end message queue or chat
server only needs to be accessible to Orbited, not to the public. I
don't know what kind of configuration bluehost allows, so I can't
answer more specifically.

Hope that helps,
Jacob

[jpsimons]

Regarding 1, the connection is released if you use "long polling," but
you're correct that, if you're going same domain you can use "XHR
Streaming" and the connection will stay open.

For 4, seriously dude, shared hosting is a waste of your time. It may
cost $2/month but if you're writing network applications like a comet
server, get a real virtual machine with root access like Slicehost,
EC2, whatever.

On Nov 20, 6:01 am, saurabh <sagarwal1...@gmail.com> wrote:
> Hi All,
> I am pretty new to ORBITED so please escuse me if my question is too
> weired.
> I am making it point wise to check if i had understood things
> correctly
>
> 1. As far as I understood ORBITED enabled reverse ajax ie server push
> that means the http connection
> between Clinet and server is not released and data is sent on that
> connection.
>
> 2.  Now suppose I want to make a chat kind of application then Clients
> will connected to server using simple http only ( however using
> ORBITED javascript)  and two clients can chat using some mesage queue.
>
> 3. The message queue used for communication is internal to the server
> and clients dont need to know about them.
>
> 4. [ Most Imp ] So in any case I dont require a public IP if i am
> launching a platform where people can chat.
> All Communication between client and server will happen over http so
> new need of public ip ( as dont need any listening port to listen to
> client requests over sockets)
>
> Actually I am using a shared hosting server ( bluehost ) and want to
> know if I need to get a public ip to run the chat application.
>
> Thanks
> Saurabh
>

> --http://reviewpunch.com/

[sste...@gmail.com]

On Nov 20, 2009, at 12:04 PM, jpsimons wrote:

> Regarding 1, the connection is released if you use "long polling," but
> you're correct that, if you're going same domain you can use "XHR
> Streaming" and the connection will stay open.
>
> For 4, seriously dude, shared hosting is a waste of your time. It may
> cost $2/month but if you're writing network applications like a comet
> server, get a real virtual machine with root access like Slicehost,
> EC2, whatever.

Hell, you can get a Rackspace Cloud Server for about $10/month that will run most things of normal size (that fit within 256mb of memory). Very doable if you turn off all the junk you're not using which, the way they have it set up, is very little to begin with.

S

[saurabh]

Thanks a lot for all your quick and detailed responses.

Yes I will try some dedicated server , I am just using shared hosting
for testing apps.

Thanks
Saurabh

On Nov 20, 10:07 pm, "sstein...@gmail.com" <sstein...@gmail.com>
wrote: