You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title Let local server send files, not only redirects
Priority wish Status chatting
Superseder Nosy List poeml, wildintellect
Assigned To poeml Keywords
It would be useful to use the local server (the MirrorBrain host) not only for
redirects, but also to send files, effectively turning it into a mirror.
That's currently only possible by adding a separate vhost, which needs to be
scanned like any other mirror.
Here's an idea for a feature that would make it easier:
The local host could be listed in the mirror database like any other mirror. An
identifier would be chosen that enables MirrorBrain to recognize that this
"mirror" is actually itself. Either a "magic" identifier like 'direct-delivery'
would convey this meaning, or an Apache directive "MirrorBrainLocalIdentifier"
could specify this.
Then, MirrorBrain would read the needed geographical/network data from the
mirror database like for any other mirror. During mirror selection, the mirror
would be considered as usual. When it's chosen, MirrorBrain just needs to send
the file instead of replying with a redirect.
Seems to be easy to implement to me; and potentially very useful. The local
mirror could be fully configurable and the mirror selection mechanism would
cover all the little features like network locality, priorities and so on.
History
Date User Action Args
2011-03-21 22:13:55 wildintellect set nosy: + wildintellect
2011-03-21 22:07:34 poeml create
(end of migrated issue)
The text was updated successfully, but these errors were encountered:
Issue migrated (2015-06-05) from old issue tracker http://mirrorbrain.org/issues/issue87
msg332 (view) Author: poeml Date: 2011-03-21.22:07:33
It would be useful to use the local server (the MirrorBrain host) not only for
redirects, but also to send files, effectively turning it into a mirror.
That's currently only possible by adding a separate vhost, which needs to be
scanned like any other mirror.
Here's an idea for a feature that would make it easier:
The local host could be listed in the mirror database like any other mirror. An
identifier would be chosen that enables MirrorBrain to recognize that this
"mirror" is actually itself. Either a "magic" identifier like 'direct-delivery'
would convey this meaning, or an Apache directive "MirrorBrainLocalIdentifier"
could specify this.
Then, MirrorBrain would read the needed geographical/network data from the
mirror database like for any other mirror. During mirror selection, the mirror
would be considered as usual. When it's chosen, MirrorBrain just needs to send
the file instead of replying with a redirect.
Seems to be easy to implement to me; and potentially very useful. The local
mirror could be fully configurable and the mirror selection mechanism would
cover all the little features like network locality, priorities and so on.
(end of migrated issue)
The text was updated successfully, but these errors were encountered: