orbited-users

Maybe you can help me clear up a possible misunderstanding of how
Stomp works.  In
http://cometdaily.com/2008/10/10/scalable-real-time-web-architecture-part-2-a-live-graph-with-orbited-morbidq-and-jsio/
is an example of how Stomp updates the browser with subscribed
messages.  Specifically, in the javascript code there is this line:
 stomp.connect('localhost', 61613);

Since it is javascript, I assume it is executing in the browser and
that their server is on localhost for convenience sake.  Surely in a
real situation, 'localhost' would be replaced by a server domain name
on the internet with port 61613 open.  Is this not how Stomp is
supposed to work?


On Jun 19, 1:07 pm, Michael Carter <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 19, 2009 at 12:56 PM, apocalypznow <[EMAIL PROTECTED]>wrote:
>
>
>
> > But what about Stomp?  Does it not need port 61613 ?
>
> As Nemanja Stefanovic said, a typical Orbited setup doesn't expose stomp to
> the world, only to an internal port. It doesn't much matter what the port
> is, because all of your users will be connecting to your server over port
> 80, where orbited will be listening. Orbited proxies the traffic internally
> to 61613 by default, but you're welcome to change that. There is absolutely
> no reason I can see to listen for raw stomp on port 80 though.
>
> -Michael Carter
>
>
>
> > On Jun 19, 11:33 am, Nemanja Stefanovic <[EMAIL PROTECTED]> wrote:
> > > I solved this in Apache by adding:
>
> > > <Location "/tcp">
> > >         SetHandler none
> > > </Location>
>
> > > <Location "/orbited">
> > >         SetHandler none
> > > </Location>
>
> > > ProxyPass /tcphttp://localhost:8000/tcp
> > > ProxyPass /orbited/http://localhost:8000/
>
> > > to Apache's httpd.conf (or another one that httpd.conf pulls in).
> > Obviously
> > > replace localhost with whatever your hostname...
>
> > > On Fri, Jun 19, 2009 at 1:14 PM, apocalypznow <[EMAIL PROTECTED]
> > >wrote:
>
> > > > Hi everyone,
>
> > > > I sure hope someone can help me out please.
>
> > > > Due to (corporate) firewall restrictions, I am trying to get Orbited
> > > > +Stomp to be accessible by the browser on port 80 only.  I have been
> > > > looking at configuring HAProxy as a reverse proxy that opens only port
> > > > 80 to the browser, and depending on the request, forwards it to the
> > > > appropriate backend (ie: Stomp on 61613).  A sample HAProxy
> > > > configuration can be found here:
> > > >http://www.olivepeak.com/blog/posts/read/free-your-port-80-with-haproxy
>
> > > > In that configuration which I am listing here:
>
> > > > frontend http_proxy
> > > > bind 8.12.42.103:80
> > > > mode http
> > > > timeout client 5m
> > > > option forwardfor
> > > > default_backend apache
> > > > acl req_pubsub_path path_beg /subscriptions/channel/
> > > > acl req_notes hdr_dom(host) -i notes.olivepeak.com
> > > > use_backend pubsubs if req_pubsub_path req_notes
>
> > > > the default backend is an apache server, but if the http request is to
> > > > a path "/subscriptions/channel/" and has a certain header, then
> > > > HAProxy sends the request to another server (in this case, "pubsubs" -
> > > > which is a Twisted server).
>
> > > > I believe that Orbited could be set up similarly, but I get stuck on
> > > > how Stomp would work.  Is Stomp really just going over http?  If that
> > > > is the case, is there a way in which to look at what stomp is sending
> > > > to figure out it is a request to be sent to a Stomp listener on the
> > > > server?
>
> > > > Other than using HAProxy, has anyone else been able to tackle this
> > > > problem of needing to serve everything off port 80 with Stomp included?
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Orbited discussion group.
To post, send email to
    <[EMAIL PROTECTED]>
To unsubscribe, send email to
    <[EMAIL PROTECTED]>
For more options, visit
    <http://groups.google.com/group/orbited-users>
-~----------~----~----~----~------~----~------~--~---