I need to write a command protocol divided in 3 layers

Hello

I need to write a command protocol divided in 3 layers. A data link layer, a
network layer and an upper layer.

I'm programming this in C.

I would like some internet links that shows some examples of how to signal
between the different layers.

I'm planning to have different state machines in the different layers. The
state machines are called by an interrupt timer every 1ms.

They are going to send signals (reguests, indications and confirmation).

What is the best way to write the signaling?

In message <49f9fc17$0$90265$>, billy
<> writes
>Hello
>
>I need to write a command protocol divided in 3 layers. A data link
>layer, a network layer and an upper layer.
>
>I'm programming this in C.
>
>I would like some internet links that shows some examples of how to
>signal between the different layers.
>
>I'm planning to have different state machines in the different layers.
>The state machines are called by an interrupt timer every 1ms.
>
>They are going to send signals (reguests, indications and confirmation).
>
>What is the best way to write the signaling?
>

Is it September already ?

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

> Is it September already ?

No, silly man. Did you think so? :-P

In message <>, Grant Edwards
<> writes
>On 2009-04-30, Chris H <> wrote:
>> In message <49f9fc17$0$90265$>, billy
>>
>>>I need to write a command protocol divided in 3 layers. A data
>>>link layer, a network layer and an upper layer.
>>>
>>>[...]
>>>
>>>They are going to send signals (reguests, indications and
>>>confirmation).
>>>
>>>What is the best way to write the signaling?
>>
>> Is it September already ?
>
>It's always September somewhere...

I though it was always mid-day somewhere.....

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

billy wrote:
> Hello
>
> I need to write a command protocol divided in 3 layers. A data link
> layer, a network layer and an upper layer.
>
> I'm programming this in C.
>
> I would like some internet links that shows some examples of how to
> signal between the different layers.
>
> I'm planning to have different state machines in the different layers.
> The state machines are called by an interrupt timer every 1ms.
>
> They are going to send signals (reguests, indications and confirmation).
>
> What is the best way to write the signaling?
>
Callbacks using function pointers and object handles.

> Callbacks using function pointers and object handles.

Thank you.

I found something about protothreads that can be used to simplify the state
machines.

http://www.sics.se/~adam/pt/expansion-print.html

This is maby something I can use. :-)

billy wrote:
>
>> Is it September already ?
>
> No, silly man. Did you think so? :-P

He seems to be correct in his speculation.

--
[mail]: Chuck F (cbfalconer at maineline dot net)
[page]: <http://cbfalconer.home.att.net>
Try the download section.

billy wrote:

> I found something about protothreads that can be used to simplify the state
> machines.
>
> http://www.sics.se/~adam/pt/expansion-print.html
>
> This is maby something I can use. :-)

Is this a homework? As the article wrote, this is weird code, don't use it.
The simplest solution for a statemachine would be to use an enum with
meaningful names and just a big switch-case.

I assume Edwin means something like the state pattern, as you can implement
it easily in object oriented languages like C++, Java or Lisp:

http://en.wikipedia.org/wiki/State_pattern

In C you'll need function pointers and object handles.

--
Frank Buss,
http://www.frank-buss.de, http://www.it4-systems.de

> Is this a homework? As the article wrote, this is weird code, don't use
> it.

No

On Sat, 02 May 2009 07:52:58 -0500, Grant Edwards wrote:

>> As the article wrote, this is weird code, don't use it.
>
> Why not?

It produces illegible code. Actually, it's worse than that, as it's likely
to trick you into thinking that you know what the code is doing.

C macros are an abomination at the best of times, but macros which expand
to partial control structures are much, much worse.

> I've used protothreads in products, and it works very
> nicely. You end up with code that's a lot more readable and
> more easily maintained than complex, explicit state machines.

Most things are more readable than an explicit state machine. But the
protothreads code has to be one of the few cases which aren't; what the
code appears to be doing and what it's actually doing are very different
things. At least with an explicit state machine you'll probably know that
you don't understand it, rather than deceiving yourself into thinking that
you do.