WebSphere Components - Context Structure: where to put branch data? And what about

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Components > January 2004 > Context Structure: where to put branch data? And what about





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Context Structure: where to put branch data? And what about
Tony Carlier

2004-01-19, 10:34 am

Hello,

We are starting to develop a new BTT application and we are struggling
with the following problem: where will we put our branchData?

We would like that all users of the same branch use the same
branchContext. So that's why we think about the following structure:

ServerContext
|
BranchContext
|
htmlSessionContext
|
UserContext
|
...

Now we have the following questions:
1) The data that are in the htmlSessionContext don't have anything to do
with the business. So wouldn't it be better that the htmlSessionContext
is not part of this hierarchy? Then we would have:

ServerContext
|
BranchContext
|
UserContext
|
...

with the htmlSessionContext chained directly to the ServerContext. In
this case the context doesn't have to be modified for any other channel.

2) If we suppose that the htmlSessionContext is in the hierarchy, how
will the BranchContext be initialized? Is it possible to initialize the
BranchContexts for all branches at once in the StartServerServlet? Or is
it better that the BranchContext is initialized when the first user of
the branch logs on? How can the BranchContext for the second user in the
branch be found?

Maybe the different things I describe here are possible. Or maybe not.

If all those options are possible, is there anybody who knows what's
best practice?

Many thanks in advance!

Kind regards,

Tony Carlier
IT Specialist
IBM Business Consulting Services


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com