Hi Dan, sounds like a good idea. How does 'gateway' actually listen in on the website session?
Is it simply invoked by the website with specific arguments? Tx, Martin "Dan Joseph" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > > > Quick answer: as others before me have also mentioned this cannot be done. > > > > > >has anyone found a way to keep a resource handle alive between > > page loads? > > > > > I've missed most of this thread, but thought I'd let you know what I'm > going for a socket setup right now. It may or may not fit your scenario. > > On my server, I have a process running called 'gateway'. Its a Perl script > that opens up a socket to where I want to go, and opens up a socket to > listen for information coming from the web site. > > PHP Web Site -> gateway -> Merchant Services > > This allows us to have a constant socket connection to them (they require > this), and defeats losing the connection when the php script terminates. We > only get 2 sockets with them at once. We could have up to 15 - 20 at once > being needed. This fixes that. > > You could do this all in PHP. I chose Perl for the server side because I > felt it was the way to implement it with our current setup. > > I don't know if that helps, but maybe it could give you some other things > to think about in solving this dilema. > > -Dan Joseph -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
