Note, Using Socket instead of Port

[Jan-Henrik Haukeland]

The latest checkin contains a refactoring where Socket_T is used for
all client communication, particular in the protocol tests. The
rationale for this change is to have a unified interface that is easy
to use for client communication and to hide the more gory details,
especially the ssl stuff from the main code base.

Unfortunately the possibility to use a certain request in the
protocols was also removed. (Only the http protocol test used this
now). I will reintroduce it back again, probably by adding an optional
request parameter to the protocol check routine as in:

   struct myprotocol {
    const char *name;                     
    int(*check)(Socket_T socket, char *request); 
  } *protocol;


-- 
Jan-Henrik Haukeland