Artyom skrev:
- Make request abstract class rather then concept. Unless you want to recompile your application to work with each type of connection.
An abstraction layer can always be build around a low-level template code. Going the other way is impossible, so please avoid virtual functions as the only choice.
Have you ever written FastCGI/SCGI application?
Nope.
If so can you please give me any rationale what is the difference (from application point of view) between
- FastCGI over TCP/IP - FastCGI over Unix Domain Sockets? - SCGI over TCP/IP - SCGI over Unix Domain Sockets?
If so give me one reason why should my application be compiled for each type of these?
Good luck :-)
(I pressume you want the library to include a compiled binary witht the implementation hidden behind pimpls) Why should I be forced to link with code I don't use or rely on virtual functions, if I only need one of the above? -Thorsten