I was playing with a perl program that would use named pipes to talk to a phantom, which would do the read/writing/selecting etc and pass it back to the perl program again through a name pipe.
There would be a perl subroutines that would send/receive command to the local perl listener, and convert the data into hased arrays and varibles depending on what was used. I stopped working with UV at the time, but now I'm back,so I'll most likely finish that up. Basically, the phantom program would track the files and records in use and lock if needed (and of course unlock after a set amount of time went by and not unlocked). It would have been kludgy, but it would have gotten the job done. I was creating it so a website could access data directly from UV via a .cgi George > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Rex Gozar > Sent: Friday, October 24, 2008 2:01 PM > To: u2-users@listserver.u2ug.org > Subject: Re: [U2] [UV] PHP/Perl > > > Jeff, Charles, > > I basically used the same strategy when I wrote u2pipe, which is a C > program that uses InterCall to connect with the U2 database. To add > functionality, I add a Unibasic subroutine and a method in > whatever web > language -- right now ColdFusion and PHP, and looking to add > ASP.NET soon. > > U2pipe relies on an external socket listener: xinetd for linux, inetd > for AIX, and wininetd for Windows. The socket listener does > not have to > be on the same machine as U2 as long as it's "reachable" via the > network. Using config files, multiple connections can be made (one > socket port mapped to one U2 connection). I'm working on a > connection > pooling version, but it's not ready for prime time. > > The web server doesn't need to be on the same network. All of our > deployments use a remote web hosting solution. So the web server is > hosted in one state, while the actual U2 database is in another. > > The code and documentation is on www.PickWiki.com. > > Jeff Butera wrote: > > In a nutshell, I wrote a small C program which leverages > Intercall to make > > connections to the database. This is a lightweight program > which requires > > little to no maintenance. In short, the C program is > merely the connection > > between Perl and Unidata, passing commands from Perl to a > single subroutine > > on the Unidata side. That subroutine, in turn, does all > the work and then > > returns the data back to Perl. > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
