BEA WebLogic User Manual page 119

Part IV Presentation of Mobile Content
Configure URL Compression
The URLs generated by portal frameworks and other content servers are often very long. If URL
rewriting is used instead of cookies for session management, the length of these URLs is
extended further. Because the length of these URLs takes up valuable space within the limited
memory of a small device, the output visible to the user is often very limited. In extreme cases,
pages are limited to just 2 or 3 links.
To mitigate this, WebLogic Mobility Server supports URL compression, which reduces the
length of these URLs to a minimum, thereby allowing much more content to be delivered to the
device. This is especially relevant where the device has limited memory but could also be
important where limited bandwidth is an issue.
URL compression works by breaking the URL into fragments (query parameters) and replacing
the fragments in the URL with shortened tokens. These shortened tokens are used by WebLogic
Mobility Server to map a request generated from the replacement URL back to the original URL.
Examples
The following is an example of a URL of 359 characters produced by BEA WebLogic Portal:
/avitekfinancial/application?namespace=tracking&origin=searchResults.jsp&
event=link.clickContent&com.bea.event.type=com.bea.content.click.event&
com.bea.event.userid=null&com.bea.event.documentid=Avitek/DemoDocuments/Demo
Features
List.xls&com.bea.event.documenttype=AvitekDocs&contentId=Avitek/DemoDocuments/D
emo Features List.xls
With URL compression turned on in WebLogic Mobility Server, this URL would be reduced to
99 characters, which is a saving of 260 characters.
/avitekfinancial/application?2=!!3&!!4=!!5&!!6=!!7&!!8=!!9&!!10=!!11&!!12=!!13&
!!14=!!15&!!16=!!13
URL compression can be configured in the mis.properties file. The following is a sample
configuration for WebLogic Mobility Server running against a BEA WebLogic Portal server.
BEA WebLogic Mobility Server User Guide - 115