Javier Borrajo wrote:
>
> Life is hard ;-)
>
And we try to make it a better place. What a wonderful task we have! :)
> XmlRpc is useful unless you prefer to live in the ivory tower and wait for
> all the firewall admins in the world to do the right thing.
>
Well, I'd say you should support tunneling in order to get your product working
in a greater market, but you should also support the more efficient solution.
Hopefully, the tunneling will be so incredibly more inefficient that the
deployers will bug their firewall managers into opening up the necessary ports
for the faster choice. That's when you both keep the cake and eat it :)
> XmlRpc is also useful on its own merits. You may integrate VB components
> with CORBA servers buying a propietary briding product or you can use
> XmlRpc/SOAP. I prefer the latter, specially because there may not be
> a bridging product for some particular technology (ever heard of CORBA
> support for Perl? )
>
I think you should put the bridge right before the need, not all over the
design. If it's inefficient you'll decrease the overall performance, but by
bridging to the parts that need the inefficient protocols you at least only
decrease performance where it's absolutely necessary.
Then again, you might need to get your product onto the market fast, in which
case you may ignore everything I've said so far :)
cheers
/Kalle Blixt
--
In a Hong Kong supermarket: "For your convenience, we recommend courteous,
efficient self-service."
Karl-Fredrik Blixt
Computer Science student at LiTH, Sweden
Homepage: http://travel.to/kp
Telephone: +46-(0)13-47 39 206
Cellular: +46-(0)739-87 11 03
ICQ: 4744258
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
