While working on one of my projects today, I noticed that the page loads slow. And the thing that helped me debug the problem was a tool called django toolbar. It's a django application that displays the time of request, the queries that were executed, cache and other information that you can use to optimize your application.
I've been working hard to move my blog site to app engine platform. It will take me a couple more days to complete it so I won't be blogging about anything for a while
The google app engine roadmap has been publicly released. One of the things that caught my attention was the support for new runtime language. Rumors have been running around that GAE platform will be supporting both java and php but google never confirmed anything.
What if GAE supports PHP?
Both Java and PHP community will be happy but considering that PHP applications can be hosted for as low as 4 USD a month, I dont think people will easily jump from using hosting service to GAE platform.
What if GAE supports Java?
The main reason why people turn away from java is because of the high cost of its hosting. Allowing small java developers/players to host their applications for free will be fantastic.
I created a survey so you can all vote for what you think (and what you want) GAE to support next.
http://www.surveymonkey.com/s.aspx?sm=kSlGNa0ZFh2iKmq5tY7HcA_3d_3d
As I was browsing, I came across an article used to host python web applications better. The module called 'mod_wsgi' is a new&better apache module than mod_python when hosting django/python apps. I haven't personally tried it (maybe I will this coming weekend) but the comments by other people are very interesting. Anyway to give you some short round-up, this are the things that it can do:
Links:
http://code.google.com/p/modwsgi/
http://www.technobabble.dk/2008/aug/25/django-mod-wsgi-perfect-match/
http://code.djangoproject.com/wiki/django_apache_and_mod_wsgi
Here is the base class of my entities. This one supports deleting of record by marking instead of permanently deleting the record:
class BaseModel(models.Model):
"""
Base model for all entities
"""
date_created = models.DateTimeField(auto_now_add=True)
date_updated = models.DateTimeField(auto_now=True, auto_now_add=True)
def delete(self, permanent=False):
"""
Delete a model by flagging. An optional parameter 'permanent' can be passed to permanently delete it
"""
if BaseModel.__deletable_type(self.__class__) and not permanent:
self.deleted = 1
self.save()
else:
models.Model.delete(self)
@classmethod
def all(cls, include_deleted=False):
"""
Get all query object with deleted records filtered
"""
deleted_field = hasattr(cls, "deleted")
if BaseModel.__deletable_type(cls) and not include_deleted:
query = cls.objects.all()
return query.filter(deleted=False)
else:
return cls.objects.all()
@classmethod
def __deletable_type(cls, input_cls):
"""
Check if this class is deletable by flagging. The algorithm is slow so it needs some tweaking later
"""
for b in input_cls.__bases__:
if b.__name__ == 'BaseDeletableUserModel': return True
return False
class Meta:
abstract = True
class BaseDeletableModel(BaseModel):
"""
A deletable base model
"""
deleted = models.BooleanField(default=False)
class Meta:
abstract = True
The code above still needs to be improved so any kind of comments will be appreciated.
| Previous Page | <Page 2 of 6> | Next Page |
powered by:
