Hi Edward:
Here is the executive summary:
Most of the content for the community starter kit resides in the
database. The CSK uses an HttpHandler to intercept incoming requests.
It inspects the URL trying to be reached and determines what
community, section, and piece of content the request is trying to
reach. Using a technique called URL rewriting, it then internally
processes the request using the communityDefault.aspx page by
dyamically loading content and user controls into the page and sending
a response back to the user.
The CSK approach extremely flexible but it does take some time to get
your head around what is going on. The site in my signature is built
using the CSK with some modifications. There is also a book available
about the CSK (I'm a co-author):
http://www.amazon.com/exec/obidos/ASIN/1904811000/
Feel free to post more questions if you want some more detail.
--
Scott
http://www.OdeToCode.com
On Tue, 25 May 2004 10:22:43 +0800, "Edward" <zi***@citiz.net> wrote:
I've studied Portal, Report, whose whitepaper can tell the mechanism at the
first time, but Community is different.
I succeeded in localizing the page to chinese, but that experience didn't
make it clear to me, what's the mechanism of request handling?
browsers request for http://localhost/community/default.aspx , in fact it
doesn't return the true default.aspx content(because this file is designed
to one installtion error page, if installation failed, user got it)
I checked the file: web.config, there is something like:
<pagePaths>
<add key="basePage" value="/communityDefault.aspx" />
</pagePaths>
in my opinion, Community has some great feature over Portal and other kits,
however, drawbacks accompany of course.
I hope somebody will help me. thanks.
