Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

	DialUp Networking (DUN) Functions
	Error Messages
	Examples
	FTP Functions
	Get IP Address
	HTTP Functions
	s... Socket Functions
	Samples From Users
	SMTP Functions
	wx.... Functions

• !!NEWS FLASH!!
• Background Information on Sockets
• Base64 Encoding
• Changing the Timeout with wxParmSet
• Citrix Monitor
• Connect to a NNTP server
• Encoding URLs
• How Does Winsock Extender Use Ports
• How to Get GM Time from Time Servers
• How to Receive a Line with a Ctrl-C in it
• Internet Extender and Showing Web Pages
• Invalid Page Fault with Compiled EXE
• Non-DNS served IP addresses and Winsock
• NSLookup Functionality
• Pop3 Functions and File Attachments
• ScanTCP and UCP Ports for Virus or Worm
• Socket Connector and Listener Script
• SSH and WinBatch
• TCP-IP Port Definitions
• UrlEncode or iContentUrl cannot handle hebrew characters
• Using Dotted IP Addresses
• WebSite Windows CGI 1.3a Interface
• What is the PDH.DLL File Used For
• WinSock Buffer Problem
• Winsock Error 10110 and Specifying Host Name
• Winsock Extender and ASP
• Winsock Extender Virus Issue

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

WinSock Buffer Problem

---

Question:

I have extensive code that was last compiled and run in WB2001 that I’m upgrading and recompiling in WB2004F. The apps are a software distribution system where a server sends package info to hundreds or thousands of client PCs. Much of the code runs as services on the client and the server. All communication are over sockets.

The problem appears to be that the sRecvline() or sSendline has truncated the string to 1024 bytes, in spite of the fact that the call specifies 7499 byte in length. I have large chunks of code that were tested in WB2001 that use this extender in a similar way that pass longer strings than 1024 bytes.

Answer:

After some serious debugging of the Winsock functions it seems the sSendLine function seems to be the cause.

If I change it to sSendString....the sRecvLine function on the receive side is quite happy and gets all the data...

Or If I change the line to

sSendLine(socket, strcat(req,@crlf))

then it also works.

Basically the sSendLine function looks to see if you already appended a CRLF to your data. If you did, it sends the line as-is and it works. If you did not, then it appends a CRLF to the data and sends that. This is the part that seems to be failing.

Sooooo in any case it looks good for a near term fix.

A fix will be available in next Winsock dll release 11168...

---

Article ID:   W16382

File Created: 2005:02:18:12:20:08

Last Updated: 2005:02:18:12:20:08