Spwebserver: A spserver-based Web server framework

Spwebserver: A spserver-based Web server framework Blog Category:

• OpenSource Project

Application Server Framework Web network application multithreading see this topic, it is estimated that many people will ask: Why do you want to implement a Web server?

Here are a few reasons:

1. This is a Web server framework, not a full Web server. This means that Spwebserver provides a set of APIs and class libraries that can be easily integrated into existing applications. You can call Spwebserver a embedded Web server.

2. Sometimes what we need is not a powerful and complete Web server (Apache, for example), we just need a server framework that provides the most basic HTTP functionality. For example, to implement the XML-RPC,JSON-RPC server-side with A/C + +, or to implement an HTTP bind for Jabberd. In these scenarios, Apache can also be used, but using embedded Web server can simplify configuration.

3. In the following situations, Apache seems inappropriate, and embedded Web server is just right: in an existing application, the HTTP interface is used to provide some simple control and statistical functions.

Based on the above reasons, also for
1. Enrich the Spserver project (please refer to: spserver: A high concurrent server framework based on Half-sync/half-async mode);
2. Just as a good example of the spserver framework;
Therefore, a Web server framework is implemented based on the Spserver framework.

Source code Download:
Http://spserver.googlecode.com/files/spserver-0.5.src.tar.gz
Http://code.google.com/p/spserver/downloads/list

Let's look at a simple example of using Spwebserver.

Java code

2. Class Sp_httpechohandler: Public Sp_httphandler {
4. Public
6. Sp_httpechohandler () {}
8. Virtual ~sp_httpechohandler () {}
12. Virtual void handle (Sp_httprequest * request, Sp_httpresponse * response) {
14. Response->setstatuscode ( 200);
16. Response->appendcontent ( "
18. "<title>welcome to Simple http</title>"
20. "
24. char buffer[ ] = { 0};
26. snprintf (buffer, sizeof (buffer),
28. "<p>the requested URI is:%s.</p>", Request->geturi ());
30. Response->appendcontent (buffer);
34. snprintf (buffer, sizeof (buffer),
36. "<p>client IP is:%s.</p>", Request->getclientip ());
38. Response->appendcontent (buffer);
42. For ( int i = 0; i < Request->getparamcount (); i++) {
44. snprintf (buffer, sizeof (buffer),
46. "<p>param-%s =%s<p>", Request->getparamname (i),
48. Request->getparamvalue (i));
50. Response->appendcontent (buffer);
52. }
56. For ( int i = 0; i < Request->getheadercount (); i++) {
58. snprintf (buffer, sizeof (buffer),
60. "<p>header-%s:%s<p>", Request->getheadername (i),
62. Request->getheadervalue (i));
64. Response->appendcontent (buffer);
66. }
70. if (NULL! = Request->getcontent ()) {
72. Response->appendcontent ( "<p>");
74. Response->appendcontent (Request->getcontent (),
76. Request->getcontentlength ());
78. Response->appendcontent ( "</p>");
80. }
84. Response->appendcontent ( "</body>
86. }
88. };
92. Class Sp_httpechohandlerfactory: Public sp_httphandlerfactory {
94. Public
96. Sp_httpechohandlerfactory () {}
98. Virtual ~sp_httpechohandlerfactory () {}
102. Virtual Sp_httphandler * Create () Const {
104. return new Sp_httpechohandler ();
106. }
108. };
112. //---------------------------------------------------------
116. int main ( int argc, char * argv[])
118. {
120. int port = 8080;
124. Sp_server Server ( "", Port,
126. New Sp_httphandleradapterfactory ( new Sp_httpechohandlerfactory ()));
130. Server.runforever ();
134. return 0;
136. }

The above code shows an HTTP echo server, which displays the request information sent by the client on the page.

In the simplest case, using spwebserver requires implementing two classes: Subclasses of Sp_httphandler and subclasses of Sp_httphandlerfactory.
The subclass of Sp_httphandler is responsible for handling specific HTTP requests.
Subclass of Sp_httphandlerfactory assists Spserver to create a Sp_httphandler subclass instance for each connection.

In the implementation process, the Adapter model was used to adapt the Sp_httphandler and sp_httphandlerfactory to Sp_handler and sp_handleradapterfactory. These two Adapter have been implemented and do not need to be implemented by users.