sockets

Ed Hilovsky lgf at lgfcomputers.net
Tue May 15 18:16:27 PDT 2012


Wow, we always figure out a way to compensate for the fact that they can't
count sockets. ALL other systems can figure out when you CLOSE A SOCKET,
it's not in use. Unbelievable that their socket licenses are tied to filepro
processes. Maybe I'm just stupid, but I can't see how the two are tied
together. No wonder........

 -- 

Ed Hilovsky 
LGF Computers 

Main Office   : (724) 463-7633 
Toll Free         : (800) 653-8479 
Fax Number : (866) 448-5415 
Cellular           : (412) 289-1773 

email  lgf at lgfcomputers.net 


-----Original Message-----
From: filepro-list-bounces+lgf=lgfcomputers.net at lists.celestial.com
[mailto:filepro-list-bounces+lgf=lgfcomputers.net at lists.celestial.com] On
Behalf Of Boaz Bezborodko
Sent: Tuesday, May 15, 2012 6:07 PM
To: filepro-list at lists.celestial.com
Subject: Re: sockets

> 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.


_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
Subscribe/Unsubscribe/Subscription Changes
http://mailman.celestial.com/mailman/listinfo/filepro-list



More information about the Filepro-list mailing list