domain access

I am attempting to retro fit an existing site (configuration detailed below) with Domain Access and Organic Groups.

The existing site for anonymous users is and must remain the default domain (Domain id =1). The second and subsequent domains are intended ONLY for authenticated user with various roles.
Domain Access is operational with a drop-down selection list enabling movement between domains. So far, so good.

I am working on two projects at Cornell that might benefit from sharing one Drupal code base. The obvious options include:

1. Common Drupal code / shared database (using Domain Access)
2. Common Drupal code / separate databases (using Multi-site)

My questions:

• Does anyone have a recommendation about which approach is easier to maintain?
• Does the second option with separate databases make it easier to develop the multiple sites on separate time schedules?

Craig

He seguido los pasos para instalar Domain Access en mi sitio con Drupal 7.14: En mi dominio principal instalé http://drupal.org/project/domain, tal como indican las instrucciones, luego edité settings.php de mi dominio principal y agregué el siguiente código /**
* Add the domain module setup routine.
*/
include DRUPAL_ROOT . '/sites/all/modules/domain/settings.inc';

Hola, estuve probando Domain Access (http://drupal.org/project/domain) para crear un sitio mobil, http://m.misitio.com a fin de compartir el mismo contenido de mi sitio Drupal. Configuré todo al pie de la letra, modifiqué settings.php y los demás requisitos requeridos, pero recibo este mensaje: http://m.misitio.com/sites/all/modules/domain/tests/200.png is not responding as expected and may not be configured correctly at the server level. Server code 403 was returned.

Here is the structure of the site I'm setting up. One primary (or default) site with complicated functionality - ubercart, and a host of other feature-providing modules. Four or five child/additional sites with much simpler functionality and independent content. So far this would clearly call for a multisite setup.

I am transferring about 6 subscription websites with seperate domains to drupal 7. Each domain site is fairly different on the type of content (content types) and structure but all are based around the same idea of selling content as subscription. In that sense they are very similar. I wish to use the same user base across all domains and will most definitely be using a fair amount of content across these sites. As I am new to drupal I have been beating myself on which multi-site method to use.

Hola amigos,
Desde ya un gusto y gracias por estar ahí.

Estoy investigando sobre multisitios u otros metodos para un proyecto que comprende:
Un sitio central y varios sitios satélite que proveen de información a este sitio central.

E visto El modulo Domain Access y no me convence, es bueno pero no logro trabajar bien con el. Y por otro lado mi idea es que cada sitio satélite realmente tenga su propia estructura y no siempre debe ser similar a los otros.

I pray this the right forum to post this inquiry...Hello, I am using Nodestream and domain access module. I have already created the sub-domains I needed. Now my question is how to 'push' (for lack of a better word) content to a particular sub-domain so it's (the article or advert is not visible to the other sub domains.)
The Domains created are as follows Nairobi, Nakuru and Test. Basically I want the articles meant for Nakuru to be either automatically routed using Taxonomy or manually using a sub-domain list/drop down.Need I say am a novice at this. Thank you

I'm thinking about technologies and options for a new multisite, edu multidomain project. Basic idea: people buy subscriptions to create custom domain sites.

Instead of pure sites for each domain, I'm thinking of using OG and some workflows for each domain. How capable is OG for custom full domain sites? Not just subdomains, 123.mysite.com but mysite123.com and mysite345.com all under the main code OG code base?