[JDEV] reaching Jabber through firewalls

[dlb]

re: firewalls

well a proxy is probably the most robust method for managing connections
through firewalls. An alternative is to set-up either an HTTP transport or
WCS on port 80 and poll this using Flash's loadVar's method. These can be
run in parallel to the standard c2s set-up on 5222.  I'd done this w/ WCS ,
though it isn't ideal. The WCS module wouldn't always recognize the first
polling attempt , once established though it worked fine.  This was with an
early version of WCS and the Flash 5 player,  the fix is probably trivial -
I'd never debugged the WCS side to determine the problem.

good luck


>
> Thanks D,
>
> Does anyone have anything to say on this issue:
>
> > > By the way, has anyone had any luck with running Jabber on multiple
> > > ports, so that a Flash client behind a firewall can try several
> options
> > > to connect? Or has anyone tried any other methods so that users
> behind
> > > firewalls can use a Flash client?
>
> Rob
>
>
>
>
> ----- Original Message -----
> From: "dlb" <civintel at comcast.net>
> To: <jdev at jabber.org>
> Sent: Tuesday, October 22, 2002 7:12 PM
> Subject: Re: [JDEV] RFC: cross-domain Flash support
>
>
> > Hi Rob;
> >
> > Here's a technote explaining the procedure
> > http://www.macromedia.com/support/flash/ts/documents/load_xdomain.htm
> >
> > this is essentially what we'd be doing along with establishing a
> common
> > definition of the shim's methods and interface.
> >
> > I've adapted the mechanism to the FML demo client and can send you a
> copy if
> > you'd like.
> >
> > - D
> >
> > ----- Original Message -----
> > From: "Rob Davis" <lists at solarismedia.co.uk>
> > To: <jdev at jabber.org>
> > Sent: Wednesday, October 23, 2002 1:53 PM
> > Subject: Re: [JDEV] RFC: cross-domain Flash support
> >
> >
> > >
> > > Out of interest how are you loading the shim across domains? As far
> as
> > > I'm aware, not only does the Flash player not allow socket
> connections
> > > across domains, but it also prevents the loading of data or SWFs.
> > >
> > > By the way, has anyone had any luck with running Jabber on multiple
> > > ports, so that a Flash client behind a firewall can try several
> options
> > > to connect? Or has anyone tried any other methods so that users
> behind
> > > firewalls can use a Flash client?
> > >
> > > Rob
> > >
> > >
> > > ----- Original Message -----
> > > From: "dlb" <civintel at comcast.net>
> > > To: <jdev at jabber.org>
> > > Sent: Tuesday, October 22, 2002 2:37 AM
> > > Subject: Re: [JDEV] RFC: cross-domain Flash support
> > >
> > >
> > > > Thanks for the responses guys.
> > > >
> > > > I'd looked into the proxy solution a few years ago , before
> jabberd
> > > > supported Flash connections.  IMO when you consider the issues
> related
> > > to
> > > > the security , scalability , and feasibility of implementing a
> proxy
> > > of this
> > > > sort within most leased hosting arrangements , the preferable
> solution
> > > is
> > > > still to allow the user to establish a direct connection to their
> home
> > > > domain. You're both right though , this wouldn't be crazy to
> implement
> > > ,
> > > > it's just that it doesn't provide the same value to developers and
> > > users as
> > > > the shim solution.
> > > >
> > > > Ideally if the shim solution were to meet the standards of the
> various
> > > > server development teams , it could be integrated into an existing
> > > http
> > > > service. In this way the shim would be included with future
> releases.
> > > >
> > > > does that make sense ?
> > > >
> > > > - D
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "matthew c. mead" <mmead at goof.com>
> > > > To: <jdev at jabber.org>
> > > > Sent: Tuesday, October 22, 2002 8:55 PM
> > > > Subject: Re: [JDEV] RFC: cross-domain Flash support
> > > >
> > > >
> > > > > On Tue, Oct 22, 2002 at 04:09:01PM -0700, Aaron McBride wrote:
> > > > > > What about running a small app on the server that the flash
> file
> > > came
> > > > from?
> > > > > > In your example, www.hellokitty.com could run the app, and
> forward
> > > > requests
> > > > > > to jabber.org.
> > > > > >
> > > > > > This would be a lot easier to guarantee because you don't need
> to
> > > get
> > > > every
> > > > > > jabber server out there supporting it... just the ones running
> > > flash or
> > > > > > java clients.
> > > > >
> > > > > How about making the web server that serves the flash client
> HTTP
> > > > > proxy for the flash client to make connections to the
> appropriate
> > > > > remote jabber servers?  Many of the freely available clients
> already
> > > > > support HTTP proxy connections, so examples of how to do this
> should
> > > > > be readily available.  Additionally, most web servers will
> support
> > > > > being an HTTP proxy, so really it becomes solely an issue if
> > > > > configuration (and potentially authentication that an HTTP proxy
> > > > > request is coming from the flash client and not some random
> Jane's
> > > > > web browser) for the entity hosting the flash client in their
> > > > > web-app.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -matt
> > > > >
> > > > > --
> > > > > matthew c. mead
> > > > >
> > > > > http://www.goof.com/~mmead/
> > > > > _______________________________________________
> > > > > jdev mailing list
> > > > > jdev at jabber.org
> > > > > http://mailman.jabber.org/listinfo/jdev
> > > >
> > > > _______________________________________________
> > > > jdev mailing list
> > > > jdev at jabber.org
> > > > http://mailman.jabber.org/listinfo/jdev
> > > >
> > >
> > >
> > > _______________________________________________
> > > jdev mailing list
> > > jdev at jabber.org
> > > http://mailman.jabber.org/listinfo/jdev
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> >
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev