> 2. I have an ethernet connection @home and I sometimes log in to our
> private web apps from home. Any 'c00l hacker' is able to scan network
> traffic, get my session id and use it to join to my session too just
> because there is absolutely no checking who uses session. We added ip
> checking
The problem of server and application level stats is that they are
fairly easy to implement and attractive, but they're hideously
inaccurate. First you have to ignore robot traffic, then you have to
accurately sessionise, then build the reporting interface, which must
be very powerful if it is to
Also, I forgot to say, a quick grep of the Django code reveals that the
db rollback code is currently the only listener for the
got_request_exception signal. I've moved the signal dispatch line
outside of the if statement in the base handler with the effect that it
is now always dispatched as you
I've attached a new patch and got to the bottom of the test case that
failed. I'm not 100% comfortable with my diagnosis and remedy however
and I'm happy to look at it again if the solution is problematic. If a
ticket master is able to take a quick look at the patch and the notes
that would be
OK, I've added tests and documentation to the patch and removed the
default for the type argument to raw_post. All tests pass with this
patch applied to the current Django SVN version. Please let me know if
any more changes are needed.
Ben
--~--~-~--~~~---~--~~
This seems a long way to go for the want of removing a few
forward-slashes.
XHTML has become the defacto standard for Django, which is great, but
the vast majority of pages are still HTML 4. So if there's to be one
standard it should be that.
A little while ago there was a discussion[1] about test cases that post
raw data such as XML or JSON to a view. Russ suggested adding a
raw_post method to the test Client to facilitate such tests. I've
created a ticket and uploaded a patch that does just this.
> Client.raw_post(path, payload, payload_type='text/json')
+1
I have a testing apparatus, which I built for a pre-MR project, I use
it to submit SOAP-style XML requests and all kinds of stuff. I'm
looking to port the project to MR and the tests to your test framework
at some point in the
> 500 errors are bad; it's bail out time when they happen.
I disagree. For background, I have a context processor which simply
pushes a dictionary of standard items, such as URLBASE for media and
links, to all templates. It's very unlikely that an error will have
occurred which makes this a bad
Just a quick note to say I've added a ticket and patch to modify
django.views.defaults.server_error to use RequestContext instead of
Context, thus making context-processor-generated context available to
500 pages.
Ben
--~--~-~--~~~---~--~~
You received this
I think it's important to build namespace
scope in now. I fully support making everything namespaced to the
project and the app.
Afternoon, man about the Internet -- http://aftnn.org/
tem__(self, key):
"Delete a variable from the current context"
del self.dicts[0][key]
____
Afternoon, man about the Internet -- http://aftnn.org/
I have a similar problem, app dev is at http://localhost/myapp/,
deployment is at http://mywebsite.com/. I have added an URLBASE to
settings.py and that's imported and used throughout my app. It would
be nice for this to be created automatically by Django and made
available through the
On 10 Dec 2005, at 13:49, hugo wrote:
Let's try something different and first provide problem solutions,
and _then_ extract a framework out of them.
+1
Afternoon, man about the Internet -- http://aftnn.org/
UserForeignKey, which can then accept the new options? Would this be a
good place to put anything else?
Afternoon, man about the Internet -- http://aftnn.org/
15 matches
Mail list logo
