Re: tasksing and TCP sockets

[Stephen Leake <stephen_leake@acm.org>]

"Rolf" <rolf.ebert_nospam_@gmx.net> writes:

> tmoran@acm.org wrote:
>>   But it seems to me that if the object is to use TCP to emulate hardware,
>> one should design for that hardware and do whatever is needed with UDP or
>> TCP to make the best emulation.  Is the intended hardware going to be
>> polled or generate interrupts or Windows messages or what?
>
> The real sensor hardware will be directly connected to the I/O pins of
> the mcu.  I think that counts as polling.  The application code simply
> reads variables from the h/w abstraction layer.

How do those "variables" get set? 

Does one of the IO pins generate an interrupt, that triggers the h/w
abstraction layer "read all pins" function?

Or is the h/w abstraction layer a cyclic executor, driven by a clock?

How does the application know when to read the variables? By a clock,
or some interrupt/event from the h/w abstraction layer?

-- 
-- Stephe