*This is a Frontier specific question, so I hope some of you have experience with this*

Hi Everyone,

I will try to keep this as short as possible. I am building a e-commerce website for a major retailer which houses all of our sales and inventory information in an Oracle database. Daily, we transfer over some information to our MySQL database on the web server, but still house much of our business logic within packages in the database (pl/sql). The current website (the one in production) that I will be replacing, which is built in Perl, uses an RPC module (outdated and very confusing) to connect to our internal machines (also running Perl) to fetch data and call functions on Oracle. We do this because we do not want to have a direct connection to Oracle from the web server. This essentially makes our RPC calls a proxy to the database by defining only a certain set of functions that can be used.

The new site that I am creating is being built in Java, but still needs to connect to Perl (we don't run Java on our internal machines quite yet, and we have a lot of business logic in the Perl code that is currently running the site and needs to be ported over). So far I'm using this Apache XMLRPC implementation (v 2.#) in Java to connect to a Frontier daemon running in Perl. In development this has been working great! However, I have a few questions...

Do you know if the Frontier module supports multi-threading? I'm curious as to what happens when users on the website invoke multiple calls to the same function.

Is there any other Perl implementation that will work better? Currently I'm using the Frontier Daemon, but would the CGI implementation work better? How about something other than Frontier?

I realize that hardly anyone will have an answer for me, but it's a shot in the dark (since Frontier doesn't seem to have a mailing list?)

Btw, thanks for such a great product! It makes RPC calls amazingly easy to implement in any environment.

- Jon



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to