[Seaside] Re: What's the (technical) purpose of adding t/seaside/
to the path
jbjohns at libsource.com
Fri Jul 20 13:00:37 UTC 2007
Michael Lucas-Smith wrote:
> Jason Johnson wrote:
>> I think I'm a little confused here. /seaside is only in the path
>> because that's the location you configured Seaside to live on the web
>> server no? If you want it somewhere else can't you just do something
>> ma := ModuleAssembly core.
>> seaside := WAKom default.
>> ma alias: '/my/other/location' to: [ma addPlug: [:request | seaside
>> process: request ] ].
> It's different for every web server - WebToolKit, Swazoo, Kom,
> Opentalk-HTTP, Whatever Dolphin has. So it's kinda hard to write a
> tutorial for it that covers all the Seaside versions out there.
> It's also a kind of random piece of voodoo for a beginner coming on to
> the scene don't you think?
But we are talking about deploying a production application here, no?
In that case the person is going to need to know how their system
works. But yes, the web servers themselves should provide a
configuration web page in a standard location for setting this sort of
> I think the /seaside URL is a bit of a perception problem for new
> users coming in. They expect to have control of the URL mapping space
> - in fact, it looks pretty good when you see that you can register
> your class with a name and that the URL to invoke your application is
> that URL - except for this /seaside thing on the front.
> I like the advertising it gives the project - but I can't see anyone
> wanting to ever deploy with /seaside in their URL for a real app -
> which means just about everyone is going to want to remap it or
> reconfigure it to not have it. So.. my thoughts still point toward not
> having it in the first place to remove the issue completely.
But the thing is, they will probably want *something*, and as soon as
you want that you are talking about configuration. But again, I point
back to the fact that if you are deploying then someone has to know how
to deploy with your chosen web server, whether that be Apache,
Webtoolkit, Commanche, whatever. And knowing how to rewrite URLs is
part of knowing your deployment.
More information about the Seaside