🚀 go-pugleaf

Andrew Bennett [ Borland ] wrote:
> 
> T�mas Helgi J�hannsson wrote:
> >
> >     Hi!
> >
> > I have been developing a Java-applet that communicates to a server on
> > the same machine that the applet
> > is loaded from. HOW can I be sure that people behind firewalls can use
> > my applet without getting a security exception.
> > I know it can be done (for example the URL:
> > www.nba.com/games9798/aboutcourtside.html  and click on any game below
> > today's games.), but I don't know how to do implement it.
> > If you know how please respond quickly and tell me how. It would be
> > grate if you could show me some
> > code example.
> 
> This communication your game does with the server is what is
> causing the problem with firewalls.  There may not be a way around
> it, because it can be possible to configure fire walls not to let
> applets on clients behind it to communicate out.
> 
> Andrew
> --
>   Andrew Bennett
>   abennett@borland.com
> 
>   Due to my workload, personal email more than likely won't get a reply.
>   Support options are detailed at http://www.borland.com/devsupport/
>   I am unable to answer support questions via email at this time.
> 
>   Check http://www.borland.com/devsupport/jbuilder/ for FAQs and
>   additional JBuilder support related help.

   Ohh, I didn't even think about the firewall not letting things out...
there has to be some way arround this. I guess there must be someway of
having the firewall check to see if it's your applet comming through,
and if it is, then letting it through.  I mean, if you can load the
applet through the firewall, don't you think that you should be able to
communicate with that applet, maybe you would have to resolve to using
some sort of http file streaming and writing with the server....
   Any ideas?

I'm not that familiar with firewalls, but there has to be a way of doing
this.  Since the applet shouldn't be allowed to communicate with any f
the machines behind the firewall(due to the infamous sandbox), I don't
see why you wouldn't let it communicate with the machine it was
initially loaded from. It shouldn't be able to do anything harmfull to
the users behind the firewall, except maybee bring in questional
political ideads<*grin>

Clint Brewer