Re: [lwip-users] Intention of poll, tcp_output() in tcp_slowtmr()call.

[Kieran Mansley]

On Mon, 8 Mar 2004, Kieran Mansley wrote:

> On Wed, 3 Mar 2004, David Aldrich wrote:
> > [David] My inspection of the code suggests that, for user data
> > transmission, tcp_output() only gets called at the poll interval.  This
> > seems very strange.  I want to achieve high transmission rates with
> > relatively small memory; it seems to me that this demands a high poll
> > frequency.  But I have no need for a poll callback.  I guess that I can
> > either set the pollinterval to a low value (fast polling) or call
> > tcp_output() directly from my application code after tcp_write().  This
> > seems not to be ideal.
>
> That's the intention, I seem to recall, but I may have remembered wrongly.
> Last time it was brought up I think we promised to at least document this
> need to call tcp_output if you're using the event API.  The sockets API
> does this automatically, but there are reasons (I don't remember what they
> are, but I do remember people objecting) why tcp_write shouldn't call
> tcp_output itself.

Found the original bug - it's #1894.

I've added a comment to the code to explain the need to call tcp_output(),
but I'm not sure where users look for documentation these days.  Can
someone who knows where things like this (ie. how to use the raw api) are
documented mention this issue there?  (and then close bug #1894?)

Thanks

Kieran