Discuss this help topic in MsgConnect Forum

Filter: C++  Pascal  C#  VB.NET  Java  Java ME  ActiveX  DLL 



InetTransport.IncomingSpeedLimit

InetTransport     See also    


Specifies the maximum number of bytes that can be received in one second.

Declaration

[C++]
    void setIncomingSpeedLimit(unsigned long Value);
    unsigned long getIncomingSpeedLimit(void);

[Pascal]
    property IncomingSpeedLimit : longint;

[VB6]
    Property IMCXInetTransport3.IncomingSpeedLimit As Long

[ActiveX]
    HRESULT _stdcall IMCInetTransport3.IncomingSpeedLimit([in] long Value );
    HRESULT _stdcall IMCInetTransport3.IncomingSpeedLimit([out, retval] long * Value );

[C#]
    public int IncomingSpeedLimit;

[VB.NET]
    Public Property IncomingSpeedLimit As Integer

[Java]
    public void setIncomingSpeedLimit(long value);
    public long getIncomingSpeedLimit();

[Java ME]
    public void setIncomingSpeedLimit(long value);
    public long getIncomingSpeedLimit();

[DLL]
    void __stdcall MCInetTransportSetIncomingSpeedLimit(HMCInetTransport h, unsigned long value);
    unsigned long __stdcall MCInetTransportGetIncomingSpeedLimit(HMCInetTransport h);

Parameters

  • h - handle to the object that was returned by Create method

Description

    This property specifies the maximum number of bytes that can be received in one second. 0 means "no limit".
Due to the nature of MsgConnect this property lets you define "average" bandwidth load, but not maximum load per second.

Example:
Incoming limit is 1000 bytes per second. Connection has been established, but remains idle for 100 seconds. After that the sender begins to send 1000 messages, each of them being 500 bytes long. Each of messages is smaller, than the number of bytes per second, so the total number of bytes received will exceed 1000 bytes per second. extra bytes are sent because at the beginning the connection was idle and the extra bandwidth is "borrowed" from first 100 seconds. This way, you will get 100 seconds of idle time, then some seconds of high bandwidth load (until the "reserve" of first 100 seconds is used), then limited load of 500 bytes per second.

To get around this behaviour use small InactivityTime intervals, i.e. don't keep inactive connections for a long time.

See also:     InactivityTime     OutgoingSpeedLimit    

Discuss this help topic in MsgConnect Forum