You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by Dave <sn...@gmail.com> on 2008/02/03 20:06:33 UTC
Proposal: Simple Multi-domain Support
A number of people have asked for multi-domain support, i.e. the
ability to have different weblogs access by different domain names, so
I have written up the implementation that I use on my site:
http://cwiki.apache.org/confluence/x/vScB. I'm not sure that this
proposal is really what we want in Roller. Perhaps you can provide
some feedback to help refine this and make it into a useful feature
for Roller 4.1.
- Dave
Re: Proposal: Simple Multi-domain Support
Posted by Sean Gilligan <se...@msgilligan.com>.
Oops, I guess Dave did deploy as the "root". Is there a way to not
require the weblog handle in the URL? Any known obstacles to
implementing it this way in 4.1M2?
-- Sean
Sean Gilligan wrote:
> Hi Dave, et. al.
>
> Do you know of any issues with using your patch when Roller is
> deployed as the "root" webapp? (so http://photophys.com would not
> redirect to http://photophys.com/photophys ?)
Re: Proposal: Simple Multi-domain Support
Posted by Allen Gilliland <Al...@Sun.COM>.
I agree, sounds good. Go for it.
-- Allen
srinivasa marreddy wrote:
> Hi Sean,
> You proposal sounds great and makes perfect sense . Looking
> forward to see this feature in 4.1 M2.
>
> --Srini
>
>
> On 2/5/08, Sean Gilligan <se...@msgilligan.com> wrote:
>> Hi Dave, et. al.
>>
>> Do you know of any issues with using your patch when Roller is deployed
>> as the "root" webapp? (so http://photophys.com would not redirect to
>> http://photophys.com/photophys ?)
>>
>> Allen Gilliland wrote:
>>> All url building should be done using the URLStrategy, so if there are
>>> a couple places which aren't doing that then they should be fixed.
>> Sounds right to me.
>>
>>> As Srinivasa said, putting the per weblog absolute url in the static
>>> config doesn't make sense, it should be in the db and configurable at
>>> runtime. In fact, it probably makes most sense for that to be a
>>> property of a Weblog and hence in the weblog table.
>> Agreed.
>>> It sounds like there are 2 problems which may not share the same
>>> solution.
>>>
>>> Solving for the subdomain situation should be just a matter of
>>> choosing a different URLStrategy and RequestMapper which are designed
>>> to expect urls of the form blog_handle.domain.com/rest/of/url. Your
>>> proposal is more designed for solving the true multi-domain problem.
>> I think the two solutions should be developed together, and the
>> configuration should options should work as follows:
>>
>> A) Roller deployment is configured by the server administrator with the
>> following settings:
>> 1) Configurable URL strategy:
>> a) Current strategy
>> b) Subdomain strategy
>> 2) A boolean setting that enables/disables blog admins from
>> setting custom domains
>>
>> B) A Blog administrator can enable a custom domain on a per-blog basis
>> (if enabled by the server admin)
>> * Requires an additional setting on the Weblog Settings UI
>> screen (hidden when disabled)
>> * Custom domains on Weblogs might require the subdomain URL
>> strategy (?)
>> * Can Open
>>
>> I'd be willing to make these changes for "4.1M2" if people think this
>> approach makes sense.
>>
>> -- Sean
>>
>> p.s. Welcome back Allen!
>>
>>
>>
>
>
Re: Proposal: Simple Multi-domain Support
Posted by srinivasa marreddy <sr...@gmail.com>.
Hi Sean,
You proposal sounds great and makes perfect sense . Looking
forward to see this feature in 4.1 M2.
--Srini
On 2/5/08, Sean Gilligan <se...@msgilligan.com> wrote:
>
> Hi Dave, et. al.
>
> Do you know of any issues with using your patch when Roller is deployed
> as the "root" webapp? (so http://photophys.com would not redirect to
> http://photophys.com/photophys ?)
>
> Allen Gilliland wrote:
> > All url building should be done using the URLStrategy, so if there are
> > a couple places which aren't doing that then they should be fixed.
>
> Sounds right to me.
>
> >
> > As Srinivasa said, putting the per weblog absolute url in the static
> > config doesn't make sense, it should be in the db and configurable at
> > runtime. In fact, it probably makes most sense for that to be a
> > property of a Weblog and hence in the weblog table.
>
> Agreed.
> >
> > It sounds like there are 2 problems which may not share the same
> > solution.
> >
> > Solving for the subdomain situation should be just a matter of
> > choosing a different URLStrategy and RequestMapper which are designed
> > to expect urls of the form blog_handle.domain.com/rest/of/url. Your
> > proposal is more designed for solving the true multi-domain problem.
>
> I think the two solutions should be developed together, and the
> configuration should options should work as follows:
>
> A) Roller deployment is configured by the server administrator with the
> following settings:
> 1) Configurable URL strategy:
> a) Current strategy
> b) Subdomain strategy
> 2) A boolean setting that enables/disables blog admins from
> setting custom domains
>
> B) A Blog administrator can enable a custom domain on a per-blog basis
> (if enabled by the server admin)
> * Requires an additional setting on the Weblog Settings UI
> screen (hidden when disabled)
> * Custom domains on Weblogs might require the subdomain URL
> strategy (?)
> * Can Open
>
> I'd be willing to make these changes for "4.1M2" if people think this
> approach makes sense.
>
> -- Sean
>
> p.s. Welcome back Allen!
>
>
>
--
-Srini Marreddy
Re: Proposal: Simple Multi-domain Support
Posted by Sean Gilligan <se...@msgilligan.com>.
Hi Dave, et. al.
Do you know of any issues with using your patch when Roller is deployed
as the "root" webapp? (so http://photophys.com would not redirect to
http://photophys.com/photophys ?)
Allen Gilliland wrote:
> All url building should be done using the URLStrategy, so if there are
> a couple places which aren't doing that then they should be fixed.
Sounds right to me.
>
> As Srinivasa said, putting the per weblog absolute url in the static
> config doesn't make sense, it should be in the db and configurable at
> runtime. In fact, it probably makes most sense for that to be a
> property of a Weblog and hence in the weblog table.
Agreed.
>
> It sounds like there are 2 problems which may not share the same
> solution.
>
> Solving for the subdomain situation should be just a matter of
> choosing a different URLStrategy and RequestMapper which are designed
> to expect urls of the form blog_handle.domain.com/rest/of/url. Your
> proposal is more designed for solving the true multi-domain problem.
I think the two solutions should be developed together, and the
configuration should options should work as follows:
A) Roller deployment is configured by the server administrator with the
following settings:
1) Configurable URL strategy:
a) Current strategy
b) Subdomain strategy
2) A boolean setting that enables/disables blog admins from
setting custom domains
B) A Blog administrator can enable a custom domain on a per-blog basis
(if enabled by the server admin)
* Requires an additional setting on the Weblog Settings UI
screen (hidden when disabled)
* Custom domains on Weblogs might require the subdomain URL
strategy (?)
* Can Open
I'd be willing to make these changes for "4.1M2" if people think this
approach makes sense.
-- Sean
p.s. Welcome back Allen!
Re: Proposal: Simple Multi-domain Support
Posted by Allen Gilliland <Al...@Sun.COM>.
My thoughts ...
All url building should be done using the URLStrategy, so if there are a
couple places which aren't doing that then they should be fixed.
As Srinivasa said, putting the per weblog absolute url in the static
config doesn't make sense, it should be in the db and configurable at
runtime. In fact, it probably makes most sense for that to be a
property of a Weblog and hence in the weblog table.
It sounds like there are 2 problems which may not share the same
solution. In the past most people have asked for support of blog urls
by subdomain, such as myblog.domain.com. In this case a blog owner
wouldn't have the ability to set their blog url to anything they want,
it's supposed to just be handled the same way for all blogs. Your
proposal is to support blogs that can be hosted on any domain, which is
a slightly different problem.
Solving for the subdomain situation should be just a matter of choosing
a different URLStrategy and RequestMapper which are designed to expect
urls of the form blog_handle.domain.com/rest/of/url. Your proposal is
more designed for solving the true multi-domain problem.
-- Allen
srinivasa marreddy wrote:
> I think the second possibility ( Allow admins to specify pattern ) is
> really good option. Thanks in advance for adding this to 4.1 .
>
> -Sriini
>
>
> On 2/4/08, Dave <sn...@gmail.com> wrote:
>> On Feb 4, 2008 11:05 AM, srinivasa marreddy <sr...@gmail.com> wrote:
>>> Looks simple and straight forward but to add new property for every
>>> subdomain in properties file is going to be manual process. It would be
>>> great if we store the url in the database( http://
>>> screenname.rollerweblogger.org(default) or the other domain name )
>> during
>>> registration process and use it instead of property file.
>> That's a good point, I think it translates to this requirement:
>> - Allow users to set base blog URL via Roller UI (e.g. via Weblog
>> Settings page)
>>
>> Another possibility:
>> - Allow admin to specify pattern to use for blog URLs (e.g. using
>> URI template)
>>
>> - Dave
>>
>
>
>
Re: Proposal: Simple Multi-domain Support
Posted by srinivasa marreddy <sr...@gmail.com>.
I think the second possibility ( Allow admins to specify pattern ) is
really good option. Thanks in advance for adding this to 4.1 .
-Sriini
On 2/4/08, Dave <sn...@gmail.com> wrote:
>
> On Feb 4, 2008 11:05 AM, srinivasa marreddy <sr...@gmail.com> wrote:
> > Looks simple and straight forward but to add new property for every
> > subdomain in properties file is going to be manual process. It would be
> > great if we store the url in the database( http://
> > screenname.rollerweblogger.org(default) or the other domain name )
> during
> > registration process and use it instead of property file.
>
> That's a good point, I think it translates to this requirement:
> - Allow users to set base blog URL via Roller UI (e.g. via Weblog
> Settings page)
>
> Another possibility:
> - Allow admin to specify pattern to use for blog URLs (e.g. using
> URI template)
>
> - Dave
>
--
-Srini Marreddy
Re: Proposal: Simple Multi-domain Support
Posted by Dave <sn...@gmail.com>.
On Feb 4, 2008 11:05 AM, srinivasa marreddy <sr...@gmail.com> wrote:
> Looks simple and straight forward but to add new property for every
> subdomain in properties file is going to be manual process. It would be
> great if we store the url in the database( http://
> screenname.rollerweblogger.org(default) or the other domain name ) during
> registration process and use it instead of property file.
That's a good point, I think it translates to this requirement:
- Allow users to set base blog URL via Roller UI (e.g. via Weblog
Settings page)
Another possibility:
- Allow admin to specify pattern to use for blog URLs (e.g. using
URI template)
- Dave
Re: Proposal: Simple Multi-domain Support
Posted by srinivasa marreddy <sr...@gmail.com>.
Looks simple and straight forward but to add new property for every
subdomain in properties file is going to be manual process. It would be
great if we store the url in the database( http://
screenname.rollerweblogger.org(default) or the other domain name ) during
registration process and use it instead of property file.
-Srini
On 2/3/08, Dave <sn...@gmail.com> wrote:
>
> A number of people have asked for multi-domain support, i.e. the
> ability to have different weblogs access by different domain names, so
> I have written up the implementation that I use on my site:
> http://cwiki.apache.org/confluence/x/vScB. I'm not sure that this
> proposal is really what we want in Roller. Perhaps you can provide
> some feedback to help refine this and make it into a useful feature
> for Roller 4.1.
>
> - Dave
>
--
-Srini Marreddy