sockets

Boaz Bezborodko boaz at mirrotek.com
Tue May 15 15:06:36 PDT 2012


> Date: Tue, 15 May 2012 15:39:56 -0400 (EDT)
> From: Jay Ashworth<jra at baylink.com>
> Subject: Re: sockets
> To:filepro-list at lists.celestial.com
> Message-ID:
> 	<1462997.4474.1337110795977.JavaMail.root at benjamin.baylink.com>
> Content-Type: text/plain; charset=utf-8
>
> ----- Original Message -----
>> From: "Ed Hilovsky"<lgf at lgfcomputers.net>
>> I don't. I need fp to count properly when I close the socket as I was
>> told it would do.
> Based on what Ken's telling you, whomever told you that closing the
> sockets from within a clerk process released the license seat was ... er,
> what's that technical term again?
>
> Oh yeah: they were*lying*  to you.
>
> or they were just worng.
>
> You're going to have to factor out the code that does the socket work, and
> SYSTEM it off from inside your interactive *clerk, so that it can EXIT when
> it's done, and release the license.
>
> Cheers,
> -- jra
> -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think 
> RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land 
> Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274

One way of doing this was suggested by John Esak in his FilePro Survivor 
Series...
Put the variables you need in the new SYSTEM routine in environment 
variables.  From within the routine get the environment variables, run 
your socket process, and then exit when it's done.




More information about the Filepro-list mailing list