]> Kevux Git Server - fll/commit
Progress: Controller and Control sockets.
authorKevin Day <thekevinday@gmail.com>
Thu, 10 Mar 2022 04:51:29 +0000 (22:51 -0600)
committerKevin Day <thekevinday@gmail.com>
Thu, 10 Mar 2022 04:51:29 +0000 (22:51 -0600)
commitf2fc5d15808d6a128455e81b3e5d22fe636dec7c
tree1ec89d5041f645b3b77506b0beee03099e0f3c4a
parente9f52261bfd19a857346b5f520cf36fe860d012c
Progress: Controller and Control sockets.

This also adds a new FSS: FSS-000F (Simple Packet).

I decided that this needs its own specific specification to represent it.
This further helps make it clear that a Packet is not the same as a Payload.

There can still be some confusion because the FSS-000F (Simple Packet) has a Payload Block.
That Payload Block contains the FSS-000E (Payload).
That FSS-000E (Payload) has a Payload section within itself.
This means that there are three different, but very similar (and also related), contexts used for a "payload".
To try and avoid this, I refer to the payload in FSS-000F (Simple Packet) as the Payload Block.
I refer to the payload in the specifications as the FSS Payload or the FSS-000E (Payload).
I refer to the payload within the FSS-000F (Simple Packet) as the Payload Object, the Payload Content, or the payload section.
15 files changed:
build/level_0/settings
build/monolithic/settings
level_0/f_directory/data/build/settings
level_0/f_fss/c/fss/common.h
level_3/control/c/control.c
level_3/control/c/control.h
level_3/control/c/private-common.c
level_3/control/c/private-common.h
level_3/control/c/private-control.c
level_3/control/c/private-control.h
level_3/controller/c/control/private-control.c
level_3/controller/documents/packet.txt
level_3/controller/specifications/packet.txt
specifications/fss-000f.txt [new file with mode: 0644]
specifications/fss.txt