SQL Server
SQL Server
Wait for a Socket to Become Readable
See more Socket/SSL/TLS Examples
Demonstrates Socket.SelectForReading, which waits for read-ready activity on the socket, or on any contained socket when the object is a socket set. It returns 1 if ready, 0 on timeout, or -1 on error.
Background. A timeoutMs of 0 performs a nonblocking poll. With a socket set, this monitors many connections at once for readability.
Chilkat SQL Server Downloads
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
DECLARE @socket int
EXEC @hr = sp_OACreate 'Chilkat.Socket', @socket OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- Connect to the server using TLS.
DECLARE @bTls int
SELECT @bTls = 1
DECLARE @maxWaitMs int
SELECT @maxWaitMs = 5000
EXEC sp_OAMethod @socket, 'Connect', @success OUT, 'example.com', 5000, @bTls, @maxWaitMs
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @socket, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @socket
RETURN
END
-- Wait up to 5 seconds for read-ready activity on the socket (or, for a socket set, on any contained
-- socket). Returns 1 if ready, 0 on timeout, or -1 on error.
DECLARE @ready int
EXEC sp_OAMethod @socket, 'SelectForReading', @ready OUT, 5000
IF @ready < 0
BEGIN
EXEC sp_OAGetProperty @socket, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @socket
RETURN
END
IF @ready <> 1
BEGIN
PRINT 'No data became available before the timeout.'
EXEC @hr = sp_OADestroy @socket
RETURN
END
PRINT 'The socket has data ready to read.'
EXEC @hr = sp_OADestroy @socket
END
GO