Re: [ql-developers] Massive amount of job state transitions and re-scheduling

[BRANE]

>
> don't forget this is a rather simple TCP/IP implementation and apparently
> it is already hard enough to make the simplest variant working reliably
> with the garden variety of TCP/IP implementations out there.
>
> Richard

O.K. I'm not following this thread from beginning, so I don't know exactly
what hardware are we talking about, but for this detail, it probably doesn't
matter much...

So, what is a solution ? Using external interrupt ? Maybe a bit bulkier
controller with built-in Ethernet ?