I have a question about django's session/auth system and its logout method.
Whenever I want to invalidate a user session ( i.e.: calling
auth.logout(request)), django
auth system is in fact invalidating my current session id cookie, but
afterwards it sets a new session id cookie, why does it do
uth.logout ( request )? And how can I
disable that? Or maybe, someone can point to the right design pattern for
this situation.
thanks,
Victor Lima
2009/12/17 David De La Harpe Golden <david.delaharpe.gol...@ichec.ie>
> Victor Loureiro Lima wrote:.
>
> > auth system is in fact inv
2009/12/21 David De La Harpe Golden <david.delaharpe.gol...@ichec.ie>
> On Thu, Dec 17, 2009 at 03:54:02PM -0200, Victor Loureiro Lima wrote:
> > Okay, let me further explain my problem...
> >
> > My website depends heavilly on the caching system, I'm using cache_
We use django for a project in my company, and by using memcached and a few
db_index on the correct fields of my models, I was able to go from 3 request
per second, to approximatelly 300 request per second, mainly doing views
cache. I didnt resort to
per-model caching, or even NGINX and it solved
Hello,
here is my model:
Class Photo( models.Model ):
photo = models.ImageField( upload_to="mydir/" )
This class is going to be used to save Images in a gallery that are
uploaded thru a zip file, so first I verify if the zip file is valid, then I
extract all of the files to a gallery
Amazon's Cloud Computing is wonderful, its currently hosting our django
website.
Media Temple is also a good option.
att,
victor lima
2009/12/22 yummy_droid
> Hi,
>
> Has anyone had good experiences with hosting companies that I can use
> for production django apps, with
You can purge the cache whenever you need and update it accordingly.
You would then have a granular cache system ( or low-level cache ). You
would have to update the cache
whenever the object it self is updated...
Pretty common actually..
Victor Lima
2009/12/22 Continuation
You are probably calling {{ model.property.url }} or {{
model.get_absolute_url }} on some property/model (either FileField or
ImageField in case of property) of some model of yours that doesnt know how
to reverse back to its URL, so the template gives an error because it doesnt
know how to render
the deployment error e-
> mails. Maybe I should direct this to django-developers instead or file
> a ticket?
>
> On Jan 4, 6:05 pm, Victor Loureiro Lima <victorloureirol...@gmail.com>
> wrote:
> > You are probably calling {{ model.property.url }} or {{
> > model.ge
Hello,
we currently have a website running on django EC2, and its running great,
really great. We managed to handle 300 requests/s on our stress tests on a
heavy page... but, we only managed to get that after we used the django's
cache systems, before that we were running close to 10 requests/s
Yes, me too.. The benchmark were executed from another EC2 instance, so we
could ignore latency.
cheers,
victor lima
2010/1/12 Malcolm Box
> On Tue, Jan 12, 2010 at 2:46 PM, Steve McConville <
> mcconville.st...@gmail.com> wrote:
>
>> > EC2 m1.small instance, talking to
maybe its an EC2 thing?
victor lima
2010/1/12 Malcolm Box <malcolm@gmail.com>
> On Tue, Jan 12, 2010 at 2:54 PM, Victor Loureiro Lima <
> victorloureirol...@gmail.com> wrote:
>
>> Hello,
>>
>> we currently have a website running on django EC2, and
Me neither, so the question remains: Is it an EC2 thing or is it common to
django?
I know that this topic is sensitive for overall web-development frameworks
such as PHP, django, and ruby.
It would be usefull if other users of this forum could post on the
"requests/s" and give some setup info, so
0 requests/s on our stress-test, thats why I was asking
other users report so we could check if thats only happening on Malcom's and
mine install, or everybody else.
cheers,
Victor Lima
2010/1/12 CLIFFORD ILKAY <clifford_il...@dinamis.com>
> On 01/12/2010 01:12 PM, Victor Loureiro
Cache the content of the table, maybe using memcached,and only go to the DB
if needed.
Victor Lima
2010/1/12 nameless
> My table with 4 milions of rows is queried often by ajax.
> So I think a performance problems ( I am using also index ).
> Ok now take a look at the
Here is the deal:
class MyModel ( models.Model ):
title = models.CharField( max_length = 100 )
only_me = models.BooleanField( default = False )
Question: Whats the proper way to guarantee that no matter how many
MyModel's are available in the database, only one of them
will have the only_me
e_true:
> obj.only_me = False
> obj.save()
> MyModel.save(self)
>
>
> I would go for that solution. It is easy to implement, it seems clean and
> it is easy to test as well.
>
> Cheers dude!
>
> Gabriel de Carvalho Nogueira Reis
> Software De
for obj in only_me_true:
> if obj.id != self.id:
> obj.only_me = False
> obj.save()
>MyModel.save(self)
>
>
> On Friday 15 January 2010 17:01:42 Victor Loureiro Lima wrote:
> > I think that will not work,when I call th
, 2010, at 4:22 PM, Victor Loureiro Lima wrote:
>
> > Here is the deal:
> >
> > class MyModel ( models.Model ):
> > title = models.CharField( max_length = 100 )
> > only_me = models.BooleanField( default = False )
> >
> > Question: Whats the pr
metatags?
Victor Lima
2010/1/20 Reinout van Rees
> On 01/20/2010 08:41 AM, Alex_Gaynor wrote:
>
>>
>> http://djangocon.eu/ is the official website for djangocon.eu (the new
>> name).
>>
>
> Please mention the old eurodjango name somewhere on that page so that
> google can
20 matches
Mail list logo