Server:WebProxy - Revision history

Speedevil: /* Related software */

2009-07-21T13:31:34Z

‎Related software

2009-07-21T13:28:57Z

rework

2008-09-25T20:11:01Z

Category: -Server (wishlist item, be in ideas)

2008-08-31T12:58:02Z

Replacing 'Freerunner' with 'FreeRunner'

2008-08-11T18:58:20Z

‎Q&A

2008-08-11T18:53:52Z

add Q&A section

2008-08-10T16:02:27Z

2008-08-09T03:28:04Z

2008-08-09T03:26:45Z

2008-04-08T09:09:57Z

reassembly proxy/client proxy

@@ Line 48: / Line 48: @@
 ==Related software==
-* rproxy - rsync for wepbages. Failed due to lack of uptake. http://ozlabs.org/~rusty/rproxy.html
+* rproxy - rsync for wepbages. Failed due potential patent problems. http://ozlabs.org/~rusty/rproxy.html
 * Zipproxy - http://ziproxy.sourceforgehttp://ziproxy.sourceforge.net/.net/ is a related application, but does not implement the core of this proposal, which is compressing webpages based on the known contents of the users cache.

@@ Line 1: / Line 1: @@
 {{wishlist}}
-This is a brief page describing a web proxy optimised for use on devices with a reasonable amount of persistant storage, and very limited bandwidth.
 Once, each page linked to a subpage of contents, which remained static, and could be easily refreshed if it changed based on dates in the HTTP headers.
 Now, this is the case in the minority of popular sites.
 Most sites now have a substantial fraction of pages with some non-static contents.
@@ Line 12: / Line 15: @@
 Simply compressing this page using advanced compression techniques provides a useful compression - taking the page to 15K.
 A very simple test, using diff and gzip however, revealed that the variation between pages is quite small.
@@ Line 22: / Line 27: @@
 The proxy then simply sends the compressed differences between the previous and current version.
 =Q&A=
 * How does this differ from rproxy? (http://ozlabs.org/~rusty/rproxy.html)
@@ Line 32: / Line 59: @@
 ** It differs significantly from rsync/rproxy, as the core of those programs - negotiating file differences over a remote link - is not done.
 ** it does not require any negotiation over the (potentially very slow) link, and also enables the proxy to potentially send other changed pages that are referred in the changes.

← Older revision		Revision as of 20:11, 25 September 2008
Line 41:		Line 41:
	* Different profiles, depending on how the FreeRunner is connected (Wifi vs. USB vs. GPRS).		* Different profiles, depending on how the FreeRunner is connected (Wifi vs. USB vs. GPRS).
	* Traffic-measurement especially for GPRS-connection for users with limited data-amounts (for example 200MB/month) or in areas with limited data-consumption, like on commercial wifi-aps on airports and such.		* Traffic-measurement especially for GPRS-connection for users with limited data-amounts (for example 200MB/month) or in areas with limited data-consumption, like on commercial wifi-aps on airports and such.
−
−	~~[[Category:Server]]~~

@@ Line 39: / Line 39: @@
 Extended usage scenarios:
-* Different profiles, depending on how the Freerunner is connected (Wifi vs. USB vs. GPRS).
+* Different profiles, depending on how the FreeRunner is connected (Wifi vs. USB vs. GPRS).
 * Traffic-measurement especially for GPRS-connection for users with limited data-amounts (for example 200MB/month) or in areas with limited data-consumption, like on commercial wifi-aps on airports and such.
 [[Category:Server]]

@@ Line 31: / Line 31: @@
 ** It also differs in that it has perfect knowledge of the state of the cache on the mobile device.
 ** It differs significantly from rsync/rproxy, as the core of those programs - negotiating file differences over a remote link - is not done.
-** it does not require any negotiation over the (potentially very slow) link.
+** it does not require any negotiation over the (potentially very slow) link, and also enables the proxy to potentially send other changed pages that are referred in the changes.
 Other optimisations:

@@ Line 28: / Line 28: @@
 * Comparing pages, and ensuring that  any page has in fact changed before downloading, as many servers misreport pages changed when they have not.
 * Convert all jpegs to progressive, and initially only download the first 'scan' of the image, which is 1/8th the size or so. Allow the user to download the remainder of the file for full resolution by clicking on it.
-* Probably 'Ziproxy' could be extended to provide this functionality
+* Probably 'Ziproxy' (http://ziproxy.sourceforge.net/) could be extended to provide this functionality.
 Extended usage scenarios:
-* Different profiles, depending on how the Freerunner is connected (Wifi vs. USB vs. GPRS)
+* Different profiles, depending on how the Freerunner is connected (Wifi vs. USB vs. GPRS).
-* Traffic-measurement especially for GPRS-connection for users with limited data-amounts (for example 200MB/month) and optional warnings when closing in to this amount
+* Traffic-measurement especially for GPRS-connection for users with limited data-amounts (for example 200MB/month) and optional warnings when closing in to this amount.
 [[Category:Server]]

← Older revision		Revision as of 09:09, 8 April 2008
Line 22:		Line 22:

	The proxy then simply sends the compressed differences between the previous and current version.		The proxy then simply sends the compressed differences between the previous and current version.
		+
		+	''improvement: it would be better NOT to modify the client, but instead have a 'reassembly proxy' on the client, so that all http clients/user agents benefit without hacks. The reassembly proxy could then inject a cookie to keep track of page versions.''

	Other optimisations:		Other optimisations: