If I make my components wait, won't I be stalling the creation of the page? Under heavy loads, how feasible will that be?
On 7/17/06, James Carman <[EMAIL PROTECTED]> wrote:
Oh, if you're worried about simultaneous connections to the database, you don't have to worry. You can set the maximum size of your pool to some reasonable number. Then, have your components wait until a connection is available in the pool. -----Original Message----- From: Rui Pacheco [mailto:[EMAIL PROTECTED] Sent: Monday, July 17, 2006 12:05 PM To: Tapestry users Subject: Re: A bit OT: how to manage database connections for multiple components rendered simultaneously. I have several components. Each will retrieve one connection from the pool, do its thing and return it. If they are done one at the time, then its great for me. But if each user that calls the page causes 9 simultaneous connections to open, I'll need to revise my strategy. On 7/17/06, James Carman <[EMAIL PROTECTED]> wrote: > > Unless all components ask for their own connection, which I think is what > they were saying. > > -----Original Message----- > From: kranga [mailto:[EMAIL PROTECTED] > Sent: Monday, July 17, 2006 11:28 AM > To: Tapestry users > Subject: Re: A bit OT: how to manage database connections for multiple > components rendered simultaneously. > > Unless I'm missing something, you will not be using 9 connections as the > components will render in serial order. So you will make 9 requests over a > single connection. > > ----- Original Message ----- > From: "James Carman" <[EMAIL PROTECTED]> > To: "'Tapestry users'" <users@tapestry.apache.org>; "'Tapestry users'" > <tapestry-user@jakarta.apache.org> > Sent: Monday, July 17, 2006 10:19 AM > Subject: RE: A bit OT: how to manage database connections for multiple > components rendered simultaneously. > > > > All code within one request can easily just use one connection. That's > > what > > we do with Tapernate. > > > > -----Original Message----- > > From: Rui Pacheco [mailto:[EMAIL PROTECTED] > > Sent: Monday, July 17, 2006 10:13 AM > > To: Tapestry users; Tapestry users > > Subject: A bit OT: how to manage database connections for multiple > > components rendered simultaneously. > > > > Hi all > > > > This is not a pure Tapestry question, but I believe you have seen this > > before and might be able to give me some guiding light. > > > > I have a web application, which I am splitting into several fragments, > ie, > > components, each one rendering content stored in a database. I just > > realised > > my index page would have 9 such fragments and if each is to retrieve a > > connection from the pool to get its content, the stress on the db server > > might be crazy, even if each request is quite short. > > > > I have a connection pool, but even with that I don't believe its healthy > > to > > use 9 connections at the same time. What about the other users? > > > > How would you deal with this issue? > > -- > > Cumprimentos, > > Rui Pacheco > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cumprimentos, Rui Pacheco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Cumprimentos, Rui Pacheco
