i am working for
www.kalyancity.com and
www.jaheraat.com

these are two different web sites. hosted on two different server (linux).

but for these two different web site i want to make a single comman database....

so if user gets login to kalyancity.com then he should automatically login to jaheraat.com



making both web site on single server will help me?????

no, simply give access to the database on the 2 servers (if mysql, you should use 2 different users, and specify from which hosts they can connect) and make your script connect to the server the db is rather than localhost.

it's nothing more than that.
But be warned that the web site will need to comunicate with the db server through internet, and that if the 2 have connections problems, it can cause problems.
Note too that the communication between the remote site and the database will use bandwidth on both of your accounts.
From one, it's on the ascending side, and on the descending side for the other.

making both web site on single server will help me?????

It just remove the connectivity and bandwidth issues.

Well, you can surely use a common database for two websites. Even then a user logging onto kalyancity.com won't automatically be logged into jaheraat.com, the max you'll be able to offer by using a common database is that user won't have to register twice for using both of these sites.

Originally Posted by dman_2007

Well, you can surely use a common database for two websites. Even then a user logging onto kalyancity.com won't automatically be logged into jaheraat.com, the max you'll be able to offer by using a common database is that user won't have to register twice for using both of these sites.

Sure you can.
You simply must use a custom session handler that will use the DB as recipient, that will not be tied to the domain name or IP adresse.
http://www.melbournechapter.net/word...vers-with-php/
That's the way big sites who are replicated on several servers (but with 1 domain name) are handling it.

devp4:~$ host google.com
google.com has address 64.233.187.99
google.com has address 64.233.167.99
google.com has address 72.14.207.99
google.com mail is handled by 10 smtp1.google.com.
google.com mail is handled by 10 smtp2.google.com.
google.com mail is handled by 10 smtp3.google.com.
google.com mail is handled by 10 smtp4.google.com.

Been there, done that...

Originally Posted by tripy

Sure you can.
You simply must use a custom session handler that will use the DB as recipient, that will not be tied to the domain name or IP adresse.
http://www.melbournechapter.net/word...vers-with-php/
That's the way big sites who are replicated on several servers (but with 1 domain name) are handling it.

devp4:~$ host google.com
google.com has address 64.233.187.99
google.com has address 64.233.167.99
google.com has address 72.14.207.99
google.com mail is handled by 10 smtp1.google.com.
google.com mail is handled by 10 smtp2.google.com.
google.com mail is handled by 10 smtp3.google.com.
google.com mail is handled by 10 smtp4.google.com.

Been there, done that...

I know about custom session handler and sharing session across multiple subdomains or sites, but the fact is unless the user uses a link (which includes session id) from one site to go to another site, session information can't be passed and this won't always be the case.

The question that I have is...if two sites are using the same database and login credentials/session/cookie info, why not just mirror the two domains and save yourself the trouble of configuring a multiple site database to begin with?

To see a similar (although not identical) concept, go to http://webmaster-talk.com (without the w w w...this is on purpose). You'll see that you get 301-redirected to www.webmaster-talk.com . This can easily be done with domains as well.

Originally Posted by dman_2007

I know about custom session handler and sharing session across multiple subdomains or sites, but the fact is unless the user uses a link (which includes session id) from one site to go to another site, session information can't be passed and this won't always be the case.

It's a lot harder to share an authenticated session across multiple domain names, but I think our friend only wants to let users share the same credentials ... even if they have to actually log in to both sites.

Originally Posted by ForrestCroce

It's a lot harder to share an authenticated session across multiple domain names, but I think our friend only wants to let users share the same credentials ... even if they have to actually log in to both sites.

That's what i said in my first post (ability to have a common login details for both sites and not having to register twice).

oki.... thanx guys.... i'll do practically then i'll let u know.... but lets hope this will help me....



thanx....