I think that you'd need to expand upon what type of server application you are intending to write?

Stevens list 9 different server designs:

  1. Iterative server (baseline measurement; no process control)
  2. Concurrent server, one fork per client
  3. Preforked, with each child calling accept
  4. Preforked, with file locking to protect accept
  5. Preforked, with thread mutex locking to protect accept
  6. Preforked, with parent passing socket descriptor to child
  7. Concurrent server, create one thread per client request
  8. Prethreaded with mutex locking to protect accept
  9. Prethreaded with main thread calling accept

Each have there advantages and disadvantages. Some are more applicable to some applications than others.

Salient information would include such things as:

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: Current Thoughts on Server/Client Best Development Strategies by BrowserUk
in thread Current Thoughts on Server/Client Best Development Strategies by rl4518

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.