Stomp::send

stomp_send

(PECL stomp >= 0.1.0)

Stomp::send -- stomp_sendفرستادن پیام

Description

شیوه شی‌گرا (متد):

public bool Stomp::send ( string $destination , mixed $msg [, array $headers ] )

شیوه رویه‌ای:

bool stomp_send ( resource $link , string $destination , mixed $msg [, array $headers ] )

فرستادن پیام به بروکر پیام.

Parameters

link

Procedural style only: The stomp link identifier returned by stomp_connect().

destination

محل فرستادن پیام

msg

پیام برای ارسال.

headers

Associative array containing the additional headers (example: receipt).

Return Values

Returns TRUE on success or FALSE on failure.

Notes

Note:

A transaction header may be specified, indicating that the message acknowledgment should be part of the named transaction.

Tip

Stomp is inherently asynchronous. Synchronous communication can be implemented adding a receipt header. This will cause methods to not return anything until the server has acknowledged receipt of the message or until read timeout was reached.

Examples

stomp_ack() را ببینید.

add a note add a note

User Contributed Notes 1 note

up
0
james dot mk dot green at gmail dot com
2 years ago
Without a receipt header your application will fire messages potentially faster than the broker can receive them at. The broker may issue failure notices however STOMP being asynchronous your client won't get to see it.

Without a receipt ActiveMQ (5.5.0) with ProducerFlowControl turned on drops messages (even persistent ones) and my application knows nothing about it (send() returned true). With receipt header specified the STOMP library handles the wait for the receipt acknowledgement for you - you are essentially automatically throttled.
To Top