Although tunneling is a quite straightforward thing
(actually it�s non-tunnelling) for HTTP-based protocols like SOAP (and hence the
ZOAP invocation layer), I wouldn�t see it as their main application
area, rather as a side effect.
SOAP
is strong when it comes to decouple interoperating representations, such as
different binary
runtime structures (Java classes, COM classes, External
Workflows, etc.) at the application level.
SOAP
is weak when you do not have to map anything, like on a purely technical level
(naming service, messaging, logging,
etc.).
Hence,
we at infor use RMI as the "technical" backbone, while we use ZOAP for
application/client communication ... coincidently we currently only need
tunnelling in the latter case!
Best,
CGJ
-----Urspr�ngliche Nachricht-----
Von: Marko �trukelj [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 24. Januar 2001 10:32
An: 'jBoss'
Betreff: [jBoss-User] Accessing JBoss through firewalls using proxiesHi,
I have a question that is very important for an application that I'm writing.
Is it possible to access jBoss through a firewall using a HTTP proxy (or possibly SOCKS)?
RMI specification is mentioning a scenario when you set up a cgi-script on a web server on port 80 to do the rmi through it, so if one can browse the internet from his machine, one can also do rmi.
Is there anything about JBoss implementation, that would interfere with that or make that unavaliable, or is it better to use ZOAP? (or is the whole matter much more complex - naming service issues separate from rmi issues).
Thanks very much for your answers,
Marko.
