🚀 go-pugleaf

Clint Brewer wrote:
> 
>    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?


The firewall in question here isn't a local firewall.  It's a remote
firewall, and the client is behind it.  No telling what machines
the firewall will allow connections to, what port numbers it might
allow, and the protocols it might let through.

Just about the only thing you can bank on is http over port 80 going
out, and a result getting returned.

Unless they have a caching proxy server.  :)


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.