+1.
Testing the RabbitMQ client (very cool, BTW) some time ago (which is
structured the same way with a single event loop), I ran into the same kind
of issues Holger describes; for example, bursts of incoming data would cause
a heartbeat to not be sent in time, and the server would drop connections
> On 19 May 2016, at 10:40, Sven Van Caekenberghe wrote:
>
> Hi Holger,
Dear Sven,
> However, you need a regular opportunity to send something out. Thinking out
> loud, what about something like
>
> StampClient>>#runWith: receiveBlock do: sendBlock
>
> where receiveBlock is like it is now,
Hi Holger,
Thanks for using Stamp, your feedback and off-list improvements. This is really
important.
Here are some general answers to the questions you asked.
First: I have not yet used a producer only scenario, in a real system. Your
questions are very valid, basically you/we have to figure
Dear Sven,
I started to use the StampClient and intend to use it to produce data but for
heartbeat and other parts I need to read from the socket as well. I wonder
about the best strategy to deal with it.
The naive approach.
[
| event sendFrame |
event := sharedQueue next.
sendFrame
