#4444: broken pipe issue
------------------------------+---------------------------------------------
Reporter: vanderkerkoff | Owner: adrian
Status: closed | Component: Core framework
Version: 0.96 | Resolution: invalid
Keywords: broken pipe 32 | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------
Changes (by anonymous):
* status: new => closed
* resolution: => invalid
Comment:
I confused myself yesterday by assuming that the development server
runserver would behave in the same manner as lighttpd and fcgi when you
throw AB at it, dumass as I am. Runserver can't handle AB tests, and if
you think about it for one second you will realise this. I just assumed
and then went to bad places from there.
I tracked ths issue down and it's nothing at all to do with Django
One of our designers had loaded webdesign into the tempalte that was being
called in.
This webdesign randomises lorem ipsum output so that the desginers can
imitate different types of text output, that was giving AB a real
headache. Removed it and django runs like the wind again.
I sincerely apologise for posting this up here, it's the wrong place but I
didn't know it at the time.
Hopefully it might help someone else at some point in time, eh Ed ;-)
--
Ticket URL: <http://code.djangoproject.com/ticket/4444#comment:2>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
