1
0
Fork 0

Misc. documentation updates - for mmsrelay and mm7

This commit is contained in:
bagyenda 2005-04-14 14:57:37 +00:00
parent bbf523d144
commit 734ef4946d
1 changed files with 25 additions and 5 deletions

View File

@ -1562,8 +1562,8 @@ function of each of these in turn.
<p>
This component (<tt>mmsproxy</tt>) is the main point of interaction between the
gateway and MMS clients. It provides an HTTP interface through which
clients can send MMS messages. The message types expected on this
gateway and MMS clients and VASPs. It provides an HTTP interface through which
clients can send MMS messages. From clients, message types expected on this
interface are typically:
<ul>
<li> Send Request: Used by client to submit an MM to the
@ -1594,9 +1594,6 @@ All the above messages are sent to the proxy as the body of an HTTP POST request
Messages are retrieved by supplying the message URL in an HTTP GET
request. When such a request is received, the proxy:
<p>
Currently, no MMbox quotas are imposed.
</p>
<ol>
<li> Locates the message: From the URL, the proxy can tell if this
@ -1617,6 +1614,29 @@ as:
result of the HTTP request.
</ol>
<p>
Currently, no MMbox quotas are imposed.
</p>
From VASPs mmsproxy expects and processes:
<ul>
<li>Send Requests: Used to submit messages for onward transmission by
Mbuni
<li> Cancellations: A previously submitted message can be cancelled if
it hasn't yet been routed to the next processor or receiver. (That is,
only messages still in the global queue can be cancelled.) Only the
original submitted can cancel a message.
<li>Replacement: A submitted message can be changed &mdash; the VASP may
supply different content, which will
then replace any content currently in
th queue.
</ul>
<br>
Note that only SOAP MM7 requests are supported at this stage.
<br>
This component must always be running.