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.
Stomp::send
stomp_send
(PECL stomp >= 0.1.0)
Stomp::send -- stomp_send — Sends a message
Açıklama
Nesne yönelimli kullanım (method):
Yordamsal kullanım:
Sends a message to the Message Broker.
Bağımsız Değişkenler
-
link -
Procedural style only: The stomp link identifier returned by stomp_connect().
-
destination -
Where to send the message
-
msg -
Message to send.
-
headers -
Associative array containing the additional headers (example: receipt).
Dönen Değerler
Başarı durumunda true, başarısızlık durumunda false döner.
Örnekler
See stomp_ack().
Notlar
Bilginize:
A transaction header may be specified, indicating that the message acknowledgment should be part of the named transaction.
İpucu
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.
add a note
User Contributed Notes 1 note
james dot mk dot green at gmail dot com ¶
13 years ago
