Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: open
The better, much more complicated way would be to make web-service calls from the second server to the primary server for all database functions. You could use SOAP, XML-RPC, REST, or any of the others. You wouldn't need to allow remote access and could authenticate (and filter out SQL injection attempts in) each call.
[edited by: Ahhk at 9:01 pm (utc) on Sep. 17, 2008]
well , i'm looking for a solution. i have two stores. one is retail lets just call it pd. it sells products through a brick and mortar location and in the near future a shopping cart application. There is also a site lets just call it blankdealer that is a wholesale platform that offers retail to the public as well if you can't supply a tax certificate. so now that i've set the stage. there are products in the brick and morter store that will be sold on the pd site. there are products that will be sold on the pd site that come from the blankdealer site. There is point of sale software in the store that has its database. there is going to be a database for the pd site. and there is going to be a database for the blankdealer site. So what i'm thinkign is using one database , creating a web application interface for the brick and mortar store (esentially a pos on the web) the shopping cart for that pd store. Adn then at that point use ONE Database to hold all the inventory. so that if i sell a blank on the pd site then its gone, i can't sell it in the store on the point of sale app. or on the pd site online. is ONE database the answer. or is some xml feed application better? i'm so new to this arena period i'm confused.
You could even have separate pricing for each site by having a pricing column for each one.
ex. id, product, sku, qty, pd_price, blank_price, etc....
The pd site would grab whatever data was need and the pd_price, and the other would do the same but with the blank_price
What I was originally talking about was based on the assumption that the two sites were on different servers - and sharing one database. If they are on the same server, then its a non-issue and pretty simple to build.