[Bese-devel] I'm simply not getting it:

Brad Anderson brad at sankaty.com
Wed Jun 22 16:01:40 UTC 2005


Marco Baringer wrote:
> 
> things worth noting:
> 
> 2) the 'page flow' of the app (the way in which the user moves from
>    one page to the next) is entirely contained in the entry-point.

Is this common practice in UCW?  In the app I'm constructing, I have
different tabs at the top of the page for the users:

public:  home, results, rules
player:  home, results, picks, user/team maint, rules
admin :  home, results, picks, user/team maint, rules, league/game
maint, send email alerts.

So I was planning on having an entry point for each tab.  But I *could*
have only one entry point and all of these tabs are components (maybe
even w/in the tabbed component).

> it all depends on how you want to structure
> your app.

Are there any reasons to do multiple entry points due to permissions and
roles listed above?  I.e. would I have public, player, and admin entry
points?  Or just do the entire site in one entry point based on the role
stored in the session's user object?

Just looking for some advice on architecture and/or best practices,
understanding I'm probably fine either way.

Cheers,
BA



More information about the bese-devel mailing list