Peter, I am looking into this same situation so I'll ask a few questions from this thread:
> Are each site going to be their separate application instance? Yes. Each site will be its own MachII application that will have access to the same Service methods that will pull from the same database. Basically as Po mentioned, these sites will simply be a different point of entry (Skin) to the exact same data. > Basically, this means you are going to deploy each site as a separate > application Yes. > If you are going to deploy each application (i.e. site) as a separate > application context, you can easily accomplish this by have a default > set of xml files (as an application base for each site) and using > Mach-II xml includes to layer in each site's customizations. I am not 100% sure how you would do this... What would you include in the default set of xml files? I have an admin application that is being used to populate the database so the sites can access this data. The sites will mainly pull data, not create it (except orders). Therefore, there are a lot of service/listener methods that will only be accessed by the admin application. Would you suggest creating a different set of listeners/ services to be included (Mach-II xml includes) in the sites? Or would you just include the original ones even though some methods won't the accessed? > Mixing request from multiple sites (the other option) in the same > application gets harder and messier as the application grows. Agreed. Thank you in advanced. -- You received this message because you are subscribed to Mach-II for CFML list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/ Wiki / Documentation / Tickets: http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/
