acmeattic-devel team mailing list archive

[Aditya Manthramurthy <aditya.mmy@xxxxxxxxx>]

On 11 July 2010 21:14, Karthik Swaminathan Nagaraj <nkarthiks@xxxxxxxxx>wrote:

>
> OK then. If firewall is such an important issue, I shall agree.
> Could someone give me an idea of how our server daemon would interact with
> a HTTPS web server? Is it something like PHP where a script is called on
> receipt of a HTTPS request? (I have no knowledge of Django or similar).
>

Django is just like writing normal python code. I was initially proposing
that we could use IPC for the https webserver to interact with the server
daemon, when you mentioned that we should probably use a network compatible
way. If we go with that, we could make the server daemon listen on a port
and use tcp - this will allow the decoupling of the core server process and
the webserver. Since we seem to have had a misunderstanding at that time,
perhaps you want to reconsider that we should stick with IPC itself for this
interaction? Specifically, how would using IPC limit scalability in the
future? Using a hard disk farm would probably be necessary on large
instances, and in that case, deploying multiple server daemons running on
different server machines would make sense. We only need to make sure that
the different daemon processes don't corrupt data because of concurrency
issues.

--
Aditya.