You can't run it in a separate memory space without having a significant performance cost for method calls. In-memory access is very fast, but a separate memory space necessitates a non-memory access. If you're running your backend on separate servers from your front end (like you would with a JSP frontend for an EJB app), then you just cope, because the advantages outweigh the disadvantages. In this case (with a single platform for the entire app), I can't see that it makes any sense to segment the memory space within an app instance.
cheers, barneyb On 9/28/05, Mehdi, Agha <[EMAIL PROTECTED]> wrote: > > Damon, > > That's my biggest worry. I thought of creating mappings for my service layer > but I first wanted to see if there was a better way to run service layer in > its own memory space where it doesn't share other applications resources. > Do you think it'd still be a performance issue if I bumped up the memory > allocation for service layer? (BTW, how do you about increasing the memory?) > > Thanks > > > Agha Mehdi > IDT - eBusiness Program Manager > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
