hello,
i am building a portal which will consist of more services [jobs, ads, mail, etc.], like Yahoo has it. i would like to hear advice from experts who went through this:
i need to assure there will only be one login and signup screen [like Yahoo!]. okay, this is easy. what is more important is that jumping from one service to another must be transparent for registered user. example: if you are in Yahoo! mail and you click classifieds, then youre in... you dont have to login again etc.
i assume whole portal will generate quite a lot of traffic. there will of course be more dedicated machines, with one PASSPORT database [for user data].
my question is: how would you keep session in each service and between services?
1) would a service use a session cookie [or session in files]
2) do you think every service should keep session data in common database for SESSION DATA should instead in 1) and update it on every page.
jumping between services
so if we go with 1), then before jumping to another service [from ads to email for example] CURRENT service must write session_id and user_id in the common database so the new service can read it and recognize this user.
and if we go with 2) then session_id is already present in common database and we dont have to be worried that new service would not recognize this user.
ah, i know its hard to understand but anyway.
i just want to be sure things work smoothly.
thanks guys!
Matjaz
matjaz@velenje.com
