By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,206 Members | 1,020 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,206 IT Pros & Developers. It's quick & easy.

Portal site architecture

P: n/a
Ok,

My company is asking me to build a portal site for managers. I think I
have it down how I will structure the app, using C# and module based
pages like in the ibuyspy portal example. I plan on using
Authorization Manager to define the roles and authentication will be
done in active directory.

My question has to do with this:
All managers have a directory already like so:
http://company-web/managers/activedirectoryUserName/

What would be the easiest way to allow users to go to the managers
webpage portal, and pull up the relevant content? Should I place an
index.aspx page that redirects to a "main" portal entrance passing the
directory accessed to grab the relevant site?

This is the only problem I am running into architecture wise, is
dealing with the users directories and redirecting portal viewers to
the appropriate portal page.

Does anyone have any advice in developing a portal of this size? The
IBuySpy portal example is just one site, this will be as many as 700
different sites, all of the content would sit in the same SQL tables
with a unique id (probably their username).

Any advice would be greatly appreciated. Thank you!
Jul 21 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.