Yeah, but this is for server side only, so the internal webapps can talk to each other.
I guess the main question is, would a message queuing systems (such as rabbitmq) combined with AMQP be more appropriate for these sorts of tasks? The webapps themselves need to respond within 0.5 - 1.0 seconds, the target average response time, so the method used by PHP and Python to talk to each other would need to be efficient (i.e. as little overhead as possible). On Fri, Jan 21, 2011 at 11:43 AM, Kenneth Gonsalves <law...@thenilgiris.com>wrote: > On Fri, 2011-01-21 at 11:32 +0000, Cal Leeming [Simplicity Media Ltd] > wrote: > > So, I have put some thought into writing the core library functions in > > Python, then exposing an API which PHP can query per request. > > sounds like what facebook is doing > -- > regards > KG > http://lawgon.livejournal.com > Coimbatore LUG rox > http://ilugcbe.techstud.org/ > > -- > 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 unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- 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 unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
