Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Exchanging LAN messages with winsock
Message
From
21/07/2009 22:44:54
 
 
To
21/07/2009 10:57:10
General information
Forum:
Visual FoxPro
Category:
ActiveX controls in VFP
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Vista
Network:
Windows XP
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01413389
Message ID:
01413676
Views:
47
>>>years ago... Into a client`s plant... I saw an instant messenger to exchange messages between users of a LAN
>>>
>>>since that I`ve wondering how hard was to have that in our VFP app.
>>>
>>>By winsock, does anyone had any experience under VFP9 that mind to share here.. I mean, any small, or even complex one IM.
>>>
>>>TIA
>>>
>>>Claudio
>>
>>Below is a link to a FAQ I wrote on Tek-Tips some years ago. The example simply sends the messages back and forth via the loopback address (127.0.0.1) but you can change those to be local ip addresses to send messages back and forth between two machines on your LAN. It is a fairly simple/straightforward example and should give you the basics you need...
>>
>>http://www.tek-tips.com/faqs.cfm?fid=3883
>
>Cooooolll... exactly what I've been searching for... Thanks...
Hi Claudio

Be very very careful of the Winsock Activex as it is a heavy memory leaker. It has never been updated and still leaks like a sieve especially for an application as you want to make.

I had created an Intranet chat app in my vfp app using the winsock OCX . In testing with a couple of users it "seemed" to work. However when deployed on the server and used by many users, it started leaking memory.

Since the app was running off a server in Terminal Services it brought down 2 TS Servers in our farm before I caught it.

It was so bad that when runningthe task manager in TS you could actually see certain user's sessions memory just winding up till they crashed.

I have removed that module and never installed it again.

Please be very careful especially when using it on a LAN.

This is my experience. I would suggest you call the winsock.dll API directly rather than use the WINSOCK.OCX.

Bernard
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform