HttpClient clickstream design (4)

 

Click <br>

Focus on the following points <br>

1. Request server path --------- url <br>

2. Click the id. <br>

3. method used to send requests to the server: get, post, and file upload <br>

4. header information when sending a request to the server <br>

5. next click <br>

6. Click result <br> 6.1) Click status --------- Server Response Code <br> 6.2) response File Header <br> 6.3) sessionid <br> 6.4) response content <br> 6.5) response file body <br> 6.6) map (resparammap) of the parsed response file body <br>

7. Click starttime. <br>

8. Click the endtime. <br>

9. clickstreamcontext <br>

10. Click delay (lazy) <br>

The overall design oom is roughly as follows:

 

The above design is based on interfaces. Through our xml, It is parsed and encapsulated into the clickstream implementation class, click implementation class, and request header implementation class, in this way, if secondary development is required, whether it is an extension of the xml file model, a rewrite of the click stream processing behavior, a rewrite of the click processing behavior, or an extension of the response result, and the corresponding content re-resolution, you can easily carry out the bag amount.

 

1. If you have extended the click type (current category: Start click or not start click), you will re-define the click stream processing rules, you only need to click the stream processing behavior interface to configure the implementation in the xml file. You can set processing rules for the specified click stream.

 

2. If you want to customize a special click processing service based on your needs, you can also implement the "Click processing behavior" interface. When you configure the implementation to the corresponding xml file, changes the processing behavior of the node.

 

3. If you do not agree with the system's default method of parsing the corresponding file, you can also implement the response result parsing interface. However, no resolution solution is provided for each click, after the upgrade (or modify and implement this solution from now on)

 

In short, the current interface-oriented solution provides great convenience for your expansion and function formulation.