DNET HTTP(S) Foundation API
[1] Software Architecture Document, Version 1.1 Revision 1.4, LiMo Foundation, 11 September 2007
LiMo HTTP(S) API. This specification describes the LiMo HTTP API specification.
The HTTP API that this specification defines is that of the interface indicated as yellow in the figure below.
Network component structure
HTTPLib is designed with the basic concept as below.
HTTP handle : HTTP instance handle. The calling application can have one or more HTTP handles.
Session : Connection unit for each destination.
Transaction : An unit paired of one request and its response under the session. The response does not have to be one.
Basic concept
- Note:
- An HTTP handle, session handle and transaction handle are unique in a process.
A session handle is linked to an HTTP handle with NetHttpNewSession.
A transaction handle is linked to a session handle with NetHttpRequest.
IETF RFC 2616, "Hypertext Transfer Protocol -- HTTP/1.1", http://www.w3.org/Protocols/rfc2616/rfc2616.html
None
None
None
- Note:
- HTTP Lib is designed to utilize OpenSSL for HTTPS in LiMo Platform Release 1. An OEM could use other solution, or offer additional APIs but it is up to OEM to implement. See http://www.openssl.org/ .
- Warning:
- This HTTP API document contains descriptions about chunk transmission support. But this feature will not be supported in the LiMo Foundation Platform Release 1.
HTTPLib does not support "Content-Type: multipart" that is not accompanied by any one of "content-length," "Transfer-Encoding: chunked" or "Connection: Close." If this happens, the transaction and connection are terminated. In this case, the event NET_HTTP_EV_RECEIVED_HEADER will not be reported.
Generated on Mon Mar 31 01:01:00 2008 by
1.5.4
|