Re: Multiple domains, one webapp

Thanks for the advice. I'll go with this. I will look into how to create a module which I can use in both webapps, and I will need to find a reliable way to connect both of the webapps to the same (amazon RDS) database without running out of connections etc (I believe this will just mean working wi

Re: Multiple domains, one webapp

Or have two instances of the same application with some configuration parameter to tell it which version it should be. Norman Franke Answering Service for Directors, Inc. www.myasd.com > On Jul 30, 2015, at 4:12 PM, Thiago H de Paula Figueiredo > wrote: > > On Thu, 3

Re: Multiple domains, one webapp

On Thu, 30 Jul 2015 16:19:50 -0300, Dimitris Zenios wrote: I would definitely split it into two web applications with a common tapestry module.Any other way will result to a mess. Agreed, as that's basically two distinct web applications which just happen to be in the same server, even if

Re: Multiple domains, one webapp

I would definitely split it into two web applications with a common tapestry module.Any other way will result to a mess. On Thu, Jul 30, 2015 at 10:12 PM, Stephen Nutbrown wrote: > Hi, > > To cut a long story short, I have a website running using tapestry which > has two main areas, we will call

Multiple domains, one webapp

Hi, To cut a long story short, I have a website running using tapestry which has two main areas, we will call them "Client accounts" and "Partner accounts". The powers that be have now decided the best way forwards is to split this into two separate domains, let's call them www.clients.com and www

Re: zone.deferredZoneUpdate fires update events twice

Hi Geoff, thanks for your reply! I personally preferred the use of listeners, but i’ll definitely give it a try. What do you think about that double fired events? I'll try to check this again to make sure this isn’t a bug. My best, Stefan Am 24. Juli 2015 bei 03:03:32, Geoff Callender (geoff