TElSAMLServiceProvider.OnReceive event

TElSAMLServiceProvider.OnReceive

This event is used to read the data from the socket.

Declaration

[C#]
event TSBReceiveEvent OnReceive;
delegate void TSBReceiveEvent(Object Sender, ref byte[] Buffer, int MaxSize, out int Written);

[VB.NET]
Event OnReceive As TSBReceiveEvent
Delegate Sub TSBReceiveEvent(ByVal Sender As Object, ByRef Buffer As Byte(), ByVal MaxSize As Integer, Out Written As Integer)

[Pascal]
property OnReceive : TSBReceiveEvent;
TSBReceiveEvent = procedure(Sender : TObject; Buffer : pointer; MaxSize : Int32; out Written : Int32) of object;

[C++]
    void get_OnReceive(TSBReceiveEvent &pMethodOutResult, void * &pDataOutResult);
    void set_OnReceive(TSBReceiveEvent pMethodValue, void * pDataValue);
    typedef void (SB_CALLBACK *TSBReceiveEvent)(void * _ObjectData, TObjectHandle Sender, void * Buffer, int32_t MaxSize, int32_t &Written);

[Java]
    TSBReceiveEvent getOnReceive();
    void setOnReceive(TSBReceiveEvent Value);
    TSBReceiveEvent.Callback OnReceive = new TSBReceiveEvent.Callback() {
        public void TSBReceiveEventCallback(TObject Sender, byte[] Buffer, int MaxSize, TSBInteger Written) {
            //...
        }
    }

Parameters

Buffer - the buffer where the handler writes the data retrieved from the socket.
MaxSize - the maximum number of bytes that may be written to the buffer.
Written - the number of bytes that were actually written to the buffer.

Description

This event is fired by TElSSLClient/TElSSLServer when it needs to read some data from the socket. Usually this is caused by a call to DataAvailable(). The application should fill Buffer with a piece of data not longer than MaxSize bytes, and return the number of bytes written via the corresponding parameter.