The Pre/PostConnectionTask patch can do both outlined things, just have a little patience while Massimo reviews it (wink).
On Oct 28, 9:00 am, billf <[EMAIL PROTECTED]> wrote: > Voltron > > Thanks for that - some facts for the cookbook there I think :-) > > I'll investigate and report back. > > On Oct 28, 7:16 am, voltron <[EMAIL PROTECTED]> wrote: > > > Hi Billf, Ill try to have a go at answering :-) > > > 1. Functions in controller are called in order in the web2py > > controllers, so defining and calling , for example, a function called > > def foo() before your index() action would be executed first > > > 2. I think an appliance called "init" is alwas executed imediately as > > default if it does not find the "welcome" appliance. I use it as a > > starting point and re-directi to other appliances from there. > > > I hope I could help a bit > > > On 28 Okt., 07:47, billf <[EMAIL PROTECTED]> wrote: > > > > Coming from Java servlets, I find a couple of features useful: > > > > 1) To be able to run a method when my servlet/application is first > > > loaded. > > > > 2) To be able to specify that the servlet/application be loaded when > > > the server starts as opposed to when the first request is received. > > > Obviously, this feature is useful in avoiding first request delays if > > > the start up method is lengthy. > > > > How would I do the above in web2py? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
