Re: How informix applications are typical built ?

> > OLEDB\\ODBC\\JDBC\\ADO.NET > > 4GL > > ESQL\\C > Some programming languages support Informix connectivity using > third-party modules that use some of the above under the hood. PHP and > Python have Informix modules that are implemented in ESQL/C, Yep. > > I'm interested to know what is the most common way for the application > > to be > > built. > The plural of "anecdote" is not "data", but here goes. I use primarily > Informix 4GL (and derivatives/successors), some PHP, and whenever I can, > I use Python. The mix is probably 95% 4GL, 3% PHP, and 2% Python. 1. Lots of PHP on intranet/extranet sites using PHP's Informix support. 2. Some .NET apps using ODBC connections ('native' .NET connectivity only available on Win32. We use these when we want either a local client or PHP performance just sucks too much for the task [ putting on flame retardant suit now to protect myself from wild-eyed unshaven PHP fundamentalists - probably the biggest drawback to using PHP :) ]. 3. JDBC from workflow engine. Do things in workflow engines count as applications? 4. We have a bunch of old 4GL apps (Ick!!!). We occasionally have to modify them [fragile little bastards] but I'd never develop anything new in that environment.