[This idea is under development, comments are welcome on
RepeaterProxyDiscussion?.]
RepeaterProxy is an ApacheHttpd? mod_proxy and mod_rewrite inspired Tool for RadioUserLand.
In order to position a
DesktopWebAppServer as a companion to
RadioUserLand, it seems like it'd be convenient to put the companion web server
behind RadioUserLand. The companion
DesktopWebAppServer is accessed through
RadioUserLand as a proxy, where
RadioUserLand is possibly given an opportunity to filter & modify the request in and response out.
One instance where this is immediately useful is in
MailToRSS:
RSS feeds produced from mailbox indexes contain URLs linking to a mail message read function also provided by
MailToRSS. However,
MailToRSS uses the script URL as called at
RSS production time to form URLs linking to the read function. So, if
RadioUserLand and
MailToRSS are on the same machine, Radio will generally subscribe
MailToRSS feeds at a URL at localhost like
http://127.0.0.1:8023/MailToRSS/ .
A problem arises when a machine other than localhost (
http://127.0.0.1) is used to read
RSS feeds in
RadioUserLand. In this case, message reading links in
MailToRSS-produced feeds are broken. They point to
http://127.0.0.1:8023/MailToRSS/, instead of to the correct address with respect to the machine being used to read the
RSS feeds.
With a
RepeaterProxy in
RadioUserLand,
MailToRSS links can be constructed as relative links or transformed through the
RepeaterProxy to contain the correct address to the
RadioUserLand host.
Added benefits may include piggybacking on
RadioUserLand's security features, among others.
Just starting to capture ideas and dig into
UserTalk?.
--
LesOrchard - 04 Mar 2002
--
LesOrchard - 04 Mar 2002
