sockets

[Ed Hilovsky]

I think FP needs to be a bit more forthcoming regarding this. You sell a
socket license. (but you don't sell socket connections) If a server has a
license limit of 25 connections, and there are 25 connections, when the 26th
connection is attempted, it will fail. But when one of those 25 does a
socketclose then the 26th ( if it retried) would connect. 
You "REQUIRE" a certain method of programming to make your method work. Just
because I use a CALL statement, you can't understand that that "process" is
closed and the socket was also.

Obviously, FP is right and we all are wrong.
Simple. No wonder FP has had resounding success and is pulling in new
developers every day.
Listen to your customers.
What's the old saying - The Customer is Always Right. 

That is unless you deal with FP.

No documentation, no description, no stipulations. Just buy the license and
then we tell you how we made it work.  


No need to say any more as I see the light ( actually in this instance -
darkness)

Look at where FP is and maybe ( maybe) see that this would be a benefit to
those still using it and maybe (maybe) even attract NEW developers if you
used a more sane method and actually counted socket connections.
 -- 

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: Kenneth Brody [mailto:kenbrody at spamcop.net] 
Sent: Friday, May 18, 2012 1:34 PM
To: lgf at lgfcomputers.net
Cc: filepro-list at lists.celestial.com
Subject: Re: sockets

On 5/18/2012 1:08 PM, Ed Hilovsky wrote:
> Therein lies the problem. FP has "designated" a new way to count 
> socket connections.

That's just it...  We're *not* counting "socket connections".

> If there is a socket server and I connect to it, it shows one 
> connection. When I do a socketclose it shows 0 connections.

If there's a "socket server", then there's 1 "socket server".  If you
connect to it 50 times, there's still 1 "socket server".

> Whatever logic you are using is beyond me. Bottom line, look at what 
> people are saying. The majority say FP is wrong in the way they count 
> socket connections.

You keep making the argument "if other programs can count apples correctly,
why can't filePro count them correctly", and my answer has consistently been
"we don't count apples, we count apple baskets, and we count them just
fine".

> Once I open a socket in filepro, you count that process that 
> connect(ed).

No, it doesn't, as it doesn't count connections.

> Then even if I don't have an active socket open and connected, you are 
> counting it against the license. You say this as though all of us 
> should just understand that the socket license was always sold linked 
> to fp processes.

Let's say you buy a 16-user runtime license.  You have a process that uses
the main file and 5 others via lookups.  Do you use 1 runtime license or 6?

> Well, I never saw that. I was never
> give that interpretation. I was just told the price and that I needed 
> a development socket license also. So, without a firm disclaimer about 
> how FP counts, I use what the rest of the world does. And the rest of 
> the world doesn't link socket connections to anything other than 
> connect and socketclose. It's simple, connect to a socket at a 
> specific port and IP and when done do a socketclose. Period...............

If we were licensing connections, I'd agree with you.  But, that's not what
is being counted.

--
Kenneth Brody