Re: please help me enter the modern age
Posted in 2000
Topics: Connectivity: ODBC / JDBC / .NET, Connectivity: ESQL/C, 4GL & Embedded SQL, Migration, Import/Export & Data Conversion, Java & JDBC Development
I think you could try some other technologies, like: - Java servlets (look at JRun or just java module for Apache) - You can try looking at fastCGI (although I didn't work with it and I'm not sure it will be good for you) - You can try partitioning your application by using an ORB (for Java you can try JavaORB or JacORB) or an application server based on EJB. Try to look at a product called Enhydra (I hope I remember its name right). Best Regards, Octav On Sat, Jan 08, 2000 at 12:43:50AM +0000, Richard Puchalsky wrote: > > <Sujit.Pal@bankofamerica.com> wrote: > > You could use PHP (compile with with-informix) or Java servlets (with > Informix > > JDBC). Both allow you to open a server connection for a session and keep > it open > > for the duration of the session. PHP being a scripting language is > obviously > > easier to implement. > > I'll try to look into PHP, thanks ... but I'm not sure if opening a server > connection for a session is what I want. If each Web hit is a separate > "session", then I would still have to fork a new process for each Web hit. > I don't know anything about PHP so I may have the wrong idea here. > > Paul Storm <paulst@rainmakersystems.com> wrote: > > My first take would be to go with PERL. You can grandfather the > > 4GL and CGI stuff, get procedures, open language support, and > > a migration path. Also PERL is freely available for download. > > Thanks again, but wouldn't this have the same problem? The Web server would > receive user-entered form data from someone's Web client, fork a Unix > process to run the Perl program, and the Perl program would presumably have > embedded SQL in it that it would send to the database server. Doesn't this > put you into the same area of having each Web hit fork a Unix process and > start a new connection to the database server? It seems like this would > replace the 4gl as CGI with Perl as CGI. That would probably be better, but > I'm trying to get rid of the CGI altogether by having the Web server be the > only database client. Or does Apache do something where you can run Perl > programs inside it without spawning separate processes? > -- Octav Chiriac Phone: (373) 2 22 99 67 NetInfo S.R.L. Fax: (373) 2 21 36 59 Chisinau (373) 2 22 84 88 Moldova, Republic of mailto:com@netinfo-moldova.com
Octav Chiriac <com@netinfo-moldova.com> wrote in message news:857d9b$e7s$1@news.xmission.com... > > I think you could try some other technologies, like: > - Java servlets (look at JRun or just java module for Apache) > - You can try looking at fastCGI (although I didn't work with it > and I'm not sure it will be good for you) Thanks, I'll look into those. It sounds like I should just look at Apache and see what works with it. (I'm pretty sure I don't want an ORB, your other suggestion, from what I've heard of them.) Will the Informix "Web integration module" or the new Informix Foundation 2000 (basically the IDS 2000 engine with the Web integration module) help with this at all? Or should I just figure out how to use the Apache Web server and one of its API languages and forget about any other Informix products other than the database engine itself?