On 14/03/2013 1:49 p.m., Alex Rousskov wrote:
I would recommend starting with this:
src/http - HTTP-specific classes used by both sides
src/CCC - classes dealing with clients (all protocols)
src/SSS - classes dealing with servers (all protocols)
Assuming that we all agree on that top-level directory naming (sub-names
TBD)...
CCC can be "client", "client_side", "ports", "incoming", "in", "accept",
or some other misleading term. I cannot think of a good one so I used a
CCC placeholder. I hope others can come up with something. Perhaps we
can do what Ubuntu did -- does "client side" sound pretty in some
popular ancient language? :-)
SSS can be "server", "server_side", "outgoing", "out", "connect", or
some other misleading term. Client arguments apply here as well.
If we delve into the biology of Squid for naming we have some options.
It is kind of appropriate to use "Loligo" for client-side (type of
Squids fished for consumer eating), and "Onykia" for server-side (type
of Squids characterised by their tentacle construction).
Amos
