By irishgringo on

I am working on a bidding system... and I wanted to get some oppinions.
Two sites.
Site one.. Bid.mysite.com... for public bidding, users must be logged in.
Site two... dealers.mysite.com... private site for dealers. Dealers must be logged in.

The workflow is this...

consumer goes to bid.mysite.com, selects a product and creates a BID_REQUEST node.
This BID_REQUEST node would be displayed in a view on the DEALER.mysite.com.

BID_REQUESTS would display in DEALER.mysite.com.
Subscribing dealers would view these BID_REQUESTS, and place bids, which will display back to the consumer.

Pretty simple idea.
This is a Drupal 7 site. I was thinking of using DOMAIN access to share data across the sites, but I think DA may be over kill as all I need to do is share nodes. I don't want the SingleSignOn.

Ideally, I would like to use a third DB of BID_REQUESTS and BIDS. The BIDS and BID REQUESTS would actually be rather complicated set of fields.
Option B is to use FEEDS from the CONSUMER site to the DEALER site, and vise versa... synching data back and forth. This has the benefit of chopping this project up into smaller projects. But I a concerned about synching. I would prefer to just have one DB.

can I get some advice from people to chime in on this with ideas please...

⋅ Categories: Drupal 7.x

Comments

jaypan’s picture

jaypan
Location Victoria, BC
commented

The domain module is your best bet. It does exactly what you want - shares nodes between sites. That's exactly what you want to do. D7 may work with other entities as well, I haven't checked.

Contact me to contract me for D7 -> D10/11 migrations.

irishgringo’s picture

irishgringo commented

and domain access and services apparently don't play nice together...
I am thinking of using views_datasource now.

Doing Native iPHONE, ANDROID, Titanium, node.js and DRUPAL. as a contractor.