soap-nhttp.h File Reference

Go to the source code of this file.


#define SOAP_NHTTP_SOAP_ACTION   "SoapAction"


herror_t soap_nhttp_server_init_args (int argc, char **argv)
herror_t soap_nhttp_server_run (void)
void soap_nhttp_server_destroy (void)
herror_t soap_nhttp_register (const char *context)
short soap_nhttp_get_port (void)
const char * soap_nhttp_get_protocol (void)
herror_t soap_nhttp_client_init_args (int argc, char **argv)
herror_t soap_nhttp_client_invoke (void *unused, struct SoapCtx *req, struct SoapCtx **res)
void soap_nhttp_client_destroy (void)

Detailed Description

Using SOAP in HTTP

This section describes how to use SOAP within HTTP with or without using the HTTP Extension Framework. Binding SOAP to HTTP provides the advantage of being able to use the formalism and decentralized flexibility of SOAP with the rich feature set of HTTP. Carrying SOAP in HTTP does not mean that SOAP overrides existing semantics of HTTP but rather that the semantics of SOAP over HTTP maps naturally to HTTP semantics.

SOAP naturally follows the HTTP request/response message model providing SOAP request parameters in a HTTP request and SOAP response parameters in a HTTP response. Note, however, that SOAP intermediaries are NOT the same as HTTP intermediaries. That is, an HTTP intermediary addressed with the HTTP Connection header field cannot be expected to inspect or process the SOAP entity body carried in the HTTP request.

HTTP applications MUST use the media type "text/xml" according to RFC 2376 when including SOAP entity bodies in HTTP messages.

See also:

Definition in file soap-nhttp.h.

Define Documentation

#define SOAP_NHTTP_SOAP_ACTION   "SoapAction"

The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request. The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.

Definition at line 69 of file soap-nhttp.h.

Function Documentation

void soap_nhttp_client_destroy void   ) 

Definition at line 455 of file soap-nhttp.c.

References httpc_destroy().

Referenced by soap_transport_client_destroy().

herror_t soap_nhttp_client_init_args int  argc,
char **  argv

Definition at line 410 of file soap-nhttp.c.

References H_OK, herror_message(), httpc_init(), log_error2, and soap_transport_add().

Referenced by soap_transport_client_init_args().

herror_t soap_nhttp_client_invoke void *  unused,
struct SoapCtx req,
struct SoapCtx **  res

short soap_nhttp_get_port void   ) 

Definition at line 463 of file soap-nhttp.c.

References httpd_get_port().

const char* soap_nhttp_get_protocol void   ) 

Definition at line 469 of file soap-nhttp.c.

References httpd_get_protocol().

herror_t soap_nhttp_register const char *  context  ) 

Definition at line 427 of file soap-nhttp.c.

References H_OK, herror_message(), httpd_register(), and log_error2.

Referenced by soap_transport_register().

void soap_nhttp_server_destroy void   ) 

Definition at line 447 of file soap-nhttp.c.

References httpd_destroy().

Referenced by soap_transport_server_destroy().

herror_t soap_nhttp_server_init_args int  argc,
char **  argv

Definition at line 208 of file soap-nhttp.c.

References H_OK, herror_message(), httpd_init(), log_error2, soap_admin_init_args(), and soap_wsil_init_args().

Referenced by soap_transport_server_init_args().

herror_t soap_nhttp_server_run void   ) 

Definition at line 441 of file soap-nhttp.c.

References httpd_run().

Referenced by soap_transport_server_run().

Generated on Thu Jan 25 23:36:04 2007 for csoap by  doxygen 1.4.6