From 4991ad3e2426ca4b7e7b781a7beb564a7a945e1b Mon Sep 17 00:00:00 2001
From: bagyenda <>
Date: Mon, 25 Apr 2005 15:55:27 +0000
Subject: [PATCH] Fixes to documentation
---
mbuni/doc/userguide.shtml | 32 ++++----------------------------
1 file changed, 4 insertions(+), 28 deletions(-)
diff --git a/mbuni/doc/userguide.shtml b/mbuni/doc/userguide.shtml
index 84e265d..69c9c6e 100644
--- a/mbuni/doc/userguide.shtml
+++ b/mbuni/doc/userguide.shtml
@@ -978,32 +978,6 @@ lists all the configuration directives
list.
-
- |
- ua-profile-cache-directory
-
- |
-
- Directory name
- (string)
- |
-
- User Agent
- Profile Cache: When an MMS client requests (via HTTP GET command) a message
- about which it has been notified, it sends its profile URL (such as
- http://nds.nokia.com/uaprof/N3650r100.xml
- for the Nokia 3650) as part
- of the HTTP request headers. The gateway should fetch the URL presented and
- parse it to figure out the client's capabilities (so-called User Agent
- Profile). It would be inefficient to fetch the profile data each time from
- an external server, therefore the gateway caches fetched profile data in the
- directory specified here. Cache entries are never expired (which is unlikely
- to be a problem). Some badly behaved MMS clients to do not submit a profile
- URL. In this case, the gateway relies on the HTTP
- Accept request headers to determine its
- capabilities.
- |
-
|
billing-library
@@ -1551,7 +1525,7 @@ request. When such a request is received, the proxy:
Locates the message: From the URL, the proxy can tell if this
is a message in the MMbox or in the in the queue for client-destined messages.
- Extracts the User Agent profile URL from the (HTTP) request
+ Extracts the User Agent Profile URL from the (HTTP) request
headers. If that is missing, the profile information is built out of
the HTTP Accept headers. The profile URL is passed to the content
adaptation module, which performs various modifications to the MM such
@@ -1563,6 +1537,8 @@ as:
Converting text to a supported character set
Removing unsupported content from the MM
+note that profile data is cached
+(in storage-directory/UserAgent_Profiles) so as not to have to fetch it each time.
The message is then packed and returned to the client as the
result of the HTTP request.
@@ -1809,4 +1785,4 @@ format.
|