[Beepcore-c-users] flow control using SEQ

[Lei Z. <lz...@ju...>]

Hi,

I'd like to get some advice on how well beepcore-c does flow control. 
 I'm running into a deadlock - my profile listener often generates large 
amount of response data, I can see that the beep layer chops up the very 
long messages and sends out only 4k bytes at one time; then it seems to 
be waiting for a SEQ frame from the peer; the peer never sends back a 
SEQ - deadlock, nobody budges an inch.

None of the profiles provided in the library needs to send out large 
messages, so I'm wondering if this part of functionality was ever tested 
(absolutely no offense).

I'll dig more.  Any advice is greatly appreicated.
Lei