Databases
StackOverflow2013
Postsdbo
POC++ design, how to represent different stages of a protocol with objects
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POC++ design, how to represent different stages of a protocol with objects
    primarykey
    data
    text
    <p>This is not so much of a technical question, but rather a c++ design question.</p> <p>Frequently it seems that I have to design programs which have to manage some a protocol which has some sort of connection, parsing stage and abstract view. Typically I try and design my programs with separation of concerns at the forefront.</p> <p>I keep ending out with "stacks" of objects, a system sits ontop of a parser, which in turns sits ontop of a connection (often there are more layers). These objects then use member function calls to call a layer below it (Tx), and uses callbacks (<code>std::function</code>, usually) to capture information coming from the other directions (Rx).</p> <p>This design seems really subpar, as it add complexity, and each layer has to have a progressively bigger constructor and so on. Also because the connection usually uses something like ASIO, the callbacks are generally on different threads so it's hard to reason about thread saftey.</p> <p>Is there a design patterm, or idiom that represent this structure/functionality better?</p> <h2>EDIT</h2> <p>A simple example</p> <pre><code>class basic_connection { basic_connection(std::string address); void send(std::string); std::function&lt;void(std::string)&gt; on_receive; }; </code></pre> <p>I have a few classes like this, which hold that layer's state, and are glue together by their public member functions and callbacks.</p> <p>The layer above this, receives command data processes for the network and calls <code>basic_connection::send</code>. And takes the raw data from <code>basic_connection</code> and converts into commands for the layer above it unprocessed.</p> <h2>EDIT2:</h2> <p>Another issue that I forgot to mention is that you end up forwarding some of the interface though the stack, for example, a top layer still needs to know the connection status.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. US0x499602D2
    1. US111111
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POC++ design, how to represent different stages of a protocol with objects
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POC++ design, how to represent different stages of a protocol with objects
      1. USArmen Tsirunyan
      1. VTFavorite
    3. VO
      singulars
      1. POC++ design, how to represent different stages of a protocol with objects
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you want to have cross-layer capabilities?
      singulars
      1. POC++ design, how to represent different stages of a protocol with objects
      1. USbitmask
    2. CO@bitmask I want the layers above and below to be able to talk to each other, the layer below doesn't really need to know it's dealing with.
      singulars
      1. POC++ design, how to represent different stages of a protocol with objects
      1. US111111
    3. COCould you provide an example object model. What sort of protocol and what do you mean by a "view of the protocol"? Also why do the constructors get increasingly complex?
      singulars
      1. POC++ design, how to represent different stages of a protocol with objects
      1. USAndrew Tomazos
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload