Sample code for 30+ languages & platforms
SQL Server

Receive a Single Byte from a Socket

See more Socket/SSL/TLS Examples

Demonstrates Socket.ReceiveByte, which reads exactly one byte and stores its numeric value in the ReceivedInt property. The argument selects signed or unsigned interpretation.

Background. Fixed-size integers and length prefixes are common building blocks for application-defined binary protocols. Byte order is selectable, with big-endian being network byte order.

Chilkat SQL Server Downloads

SQL Server
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 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

    --  Read exactly one byte.  Its numeric value is stored in the ReceivedInt property.  Passing 1
    --  interprets the byte as unsigned (0 through 255); 0 interprets it as signed.
    DECLARE @bUnsigned int
    SELECT @bUnsigned = 1
    EXEC sp_OAMethod @socket, 'ReceiveByte', @success OUT, @bUnsigned
    IF @success = 0
      BEGIN
        EXEC sp_OAGetProperty @socket, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @socket
        RETURN
      END

    EXEC sp_OAGetProperty @socket, 'ReceivedInt', @iTmp0 OUT
    PRINT 'Received byte value: ' + @iTmp0

    EXEC @hr = sp_OADestroy @socket


END
GO