Graham,
Thanks very much. That was extremely helpful.
Regards,
Richard
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To
On May 22, 2:38 am, puff <[EMAIL PROTECTED]> wrote:
> Thanks Graham and Ben for the prompt feedback. It was most helpful.
>
> > Depending on the hosting mechanism has been configured, anyDjango
> > startup may only happen the first time a request comes in. This would
> > potentially delay
Thanks Ben for responding so promptly.
> I'm probably not qualified to comment on the deeper technical issues
> mentioned here. However that said I've just taken over quite a large
> codebase that does some of this stuff, and it can be quite painful! I'd
> suggest keeping your django code as
Thanks Graham and Ben for the prompt feedback. It was most helpful.
> Depending on the hosting mechanism has been configured, any Django
> startup may only happen the first time a request comes in. This would
> potentially delay requests if the initialisation takes a while.
Our current hosting
Hi there,
I'm probably not qualified to comment on the deeper technical issues
mentioned here. However that said I've just taken over quite a large
codebase that does some of this stuff, and it can be quite painful! I'd
suggest keeping your django code as simple as possible, i.e. just to process
On May 21, 10:37 pm, puff <[EMAIL PROTECTED]> wrote:
> As part of startup, the application needs to initialize itself from a
> number of external applications. We've Googled the issue and it
> appears that it is reasonable to do this initialization by putting
> code in startup.py. Is this the
We are considering using Django as part of a HA cluster web services
application that has some near real time elements. While much of our
application seems well suited to Django some of the near real time
elements are concerns and we were hoping that this list might provide
some perspective on
7 matches
Mail list logo
