OK, I'm picking this thread up in mid-stream, but what do you mean "move the
awake-respond-sleep cycle to Servlet"?  How can a servlet call
awake/respond/sleep on itself?  Are you saying add a "run" method to Servlet
that then calls awake/respond/sleep, and Application would just call run and
leave the rest up to the servlet?

Reading back through the threads, I see this came up from a comment that
sleep wasn't getting called after an exception in respond.  I think that's a
bug and we should modify the exception mechanism to call sleep if awake
succeeds (as others pointed out).

I think I prefer having the cycle called from Application.  It seems cleaner
to me.  Otherwise, we have to have Servlet's proposed "run" mechanism catch
any exception in respond, call sleep, and then promulgate the exception back
up to Application so it can handle the error.  But what if there is an
exception in sleep?  We could more easily handle that in Application and log
it appropriately.  But it'll get lost in Servlet unless we have some logging
functionality built in there too, becuase there will be two exceptions, the
one in respond and the one in sleep.  Does that sound right?

This cycle has been in there since the beginning, and I suspect Chuck picked
it up from Webobjects or somewhere like that.  I'll let him present his
reasoons behind having the cycle and it's placement.


Jay


> -----Original Message-----
> From: Geoffrey Talvola [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 03, 2002 9:55 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [Webware-discuss] awake respond sleep cycle
> 
> 
> Ian Bicking wrote:
> > On Tue, 2002-04-02 at 16:58, Geoffrey Talvola wrote:
> > >   def _respond(self):
> > >           try:
> > >                   Page._respond(self)
> > >           except:
> > >                   self.rollbackTransaction()
> > >           else:
> > >                   self.commitTransaction()
> > > 
> > > This wouldn't catch errors that happen _during_ the awake() 
> > call.  But maybe
> > > that's OK.
> > 
> > Is there a reason why the awake/respond/sleep cycle is 
> > implemented in (I
> > believe) Application (or Response?  I forget), instead of 
> in Servlet? 
> > It seems like this only gets in the way, it never helps 
> > anything -- and
> > you have to modify WebKit to futz around with these things, 
> you can't
> > just modify your own SitePage.
> 
> Seems like a good idea to move the full awake/respond/sleep cycle into
> Servlet to me.  But there could be some good reason why it is done in
> Application that I can't think of.
> 
> Chuck?  Jay?
> 
> - Geoff
> 
> _______________________________________________
> Webware-discuss mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/webware-discuss
> 


----------------------------------------------------------------------------

This e-mail and any attachments may be confidential or legally privileged.
If you received this message in error or are not the intended recipient, you
should destroy the e-mail message and any attachments or copies, and you are
prohibited from retaining, distributing, disclosing or using any information
contained herein.  Please inform us of the erroneous delivery by return
e-mail. 

Thank you for your cooperation.

----------------------------------------------------------------------------



_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to