On Thursday, December 19, 2002, at 12:49 PM, Jefferson R. Lowrey wrote:
There's a macperl-webcgi list for specific web and cgi topic questions that aren't directly related to MacPerl or MacOS X and perl. It's very low volume, but you'll probably still get answers if you have other questions.I will join that...as long as people don't get annoyed that I'm not using MacPerl...but some of the questions I have are probably questions I would have even if I *were* using MacPerl instead. I've only been with this mailing list for a day or so but it also seems pretty low volume compared to some of the other mailing lists to which I belong. I'm not complaining, really...just an observation.
I assume that I would need to install Perl and the Proxy package on the AS/400 for that if I were to exclude the Win 2000 box from the mix? I'd certainly like to involve as few machines as possible in whatever scheme I use if only for reducing the possible points of failure.
Have you looked into DBD::Proxy (or is it DBI::Proxy?) Basically, you should be able to set up the OS X box as a webserver, and the windows box (or even your AS/400) as a database proxy, so that all the ODBC connections occur where there are drivers, and the data gets passed back and forth separately.
Yes, I was hoping that with OS X's UNIX underpinnings, there would be a flood of drivers and other software (such as IBM deciding to port Client Access for the AS/400 to OS X)...But I suppose I knew deep down that that wouldn't happen.Can anyone tell me definitely whether or not the OS X solution is a non-starter?It's not. But it's not as direct as one might hope.
Thanks for the quick response,
Cory
