Hello Ralf, A possible third option would be to bypass using sockets and use something like XML-RPC instead (which can still use the same server running) and have your 'client' issue XML-RPC requests. There's a Google code project that makes this absolutely trivial through Django, http://code.google.com/p/django-xmlrpc/
Likely that you have a specific requirement for sockets though, but I'll put it out there anyway. Cheers. On Apr 11, 7:18 am, Ralf Kistner <[EMAIL PROTECTED]> wrote: > > If you plan on communicating between these two types of services over > > TCP sockets, I don't see why that would be easier with option #2 than > > with option #1. Socket communication shouldn't have to care if the end > > points of the socket belong to the same process or two different > > processes. > > With option #2, communication could be done with direct method calls instead > of using TCP sockets. > > Anyway, I think I'll stick with option #1. > > Thanks, > Ralf --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
