So how does that work? When the shared server restarts it restart (i encounter at least once a day) and the application scope would be gone. So how should the keeping alive of the application scope work?
Then still the first request would result in a timeout, next would probably run. Or am i missing some insight here? Very interested in how this will work for you. Thanks, Marco. On Mar 3, 7:50 pm, Mark Jones <[email protected]> wrote: > The VPS solution would have to be per-client for us. We actually own > our own server co-located somewhere else but are phasing it out > because we can't handle the support requests for email and the like. > We've switched models to the client paying for hosting directly, and > we support just their website. > > > Further i am also interested if it's possible to minimize the > > application startup time, and if it would be possible to create a sort > > of light weight version for sites that are relatively simple and don't > > require extensive features. > > My only initial thoughts was simplifying the number of files that > application startup needs to parse; removing unused content types, > etc. I hesitate to try too much because I don't want to break > dependencies I am unaware of, and I have no idea how much of a gain > that would actually bring. > > Current plan is to try and keep Application timeout to several hours > and ping it via scheduled task every hour or so. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
