Re: INFORMIX cursors in shared memory

Path: emory!swrinde!cs.utexas.edu!usc!rutgers!pyrnj!pyramid!infmx!markj From: markj@informix.com (Mark Jeske(Chicago Consultan)t) Newsgroups: comp.databases.informix Message-ID: <1991Nov2.151105.3947@informix.com> Date: 2 Nov 91 15:11:05 GMT References: <1991Nov1.223846.1316@cbnewsk.att.com> Sender: news@informix.com (Usenet News) Organization: Informix Software, Inc. In article <1991Nov1.223846.1316@cbnewsk.att.com> chardin@cbnewsk.att.com (christopher.hardin) writes: >Greetings, > > Imagine a program that could be fed SQL statements like SELECT >or UPDATE and execute them in ESQL/C. Now imagine several of these >things running at the same time. It would be nice if any available >server could take up where the last one left off. Users would send >SQL statements down the pike and the next available INFORMIX server >does the request. > > Here's my question: to do this it would be nice to put the >INFORMIX cursors into shared memory. This way each sever doesn't have >to reissue SELECT statements. Can this be done? If so, how? I have >INFORMIX SE, SQL, ESQL/C Version 4.00 UD2 running UNIX SV3.2.2 on a 386 >box. You might want to look into transaction monitors such as tuxedo from usl. You can create servers that service different clients thereby breaking the normal 1-1 relationship between applications and engines. mark