acmeattic-devel team mailing list archive

[Aditya Manthramurthy <aditya.mmy@xxxxxxxxx>]

On Saturday 10 July 2010 02:15 AM, Karthik Swaminathan Nagaraj wrote:
> It looks like we are definitely on the same page!
>
> On Wed, Jul 7, 2010 at 2:55 PM, Aditya Manthramurthy 
> <aditya.mmy@xxxxxxxxx <mailto:aditya.mmy@xxxxxxxxx>> wrote:
>
>     Hi all,
>
>     After what seems to me to be a confusion because of
>     miscommunication, we've developed a picture to show the various
>     components of the s/w. It is now linked from the wiki page at:
>     http://www.nkarthiks.info/acmeattic/index.php?title=Implementation
>
>     Please go through it. Let's discuss it at least using a clearer
>     set of terms now.
>
> Why HTTPS?: (Lets forget the web interface for a moment here) Why 
> should the client daemon talk to the server using HTTPS? Isn't an SSL 
> connection over TCP sufficient? I personally do not want to involve 
> HTTP in a client-server communication where there is *no* web browser 
> involved.

I am advocating HTTPS because the particular port we use in a TCP 
connection is likely to be closed in most restricted networks (think 
universities, and corporate networks). Not so for HTTPS. Also, in a 
HTTPS connection, the certificate's authenticity is automatically 
checked with the certifying authority by the browser. I don't know how 
we would do this with plain TCP with SSL/TLS.

> IPC: When there is network, why IPC? This limits future scalability.
Ah, that is good. Maybe some custom protocol over TCP can be used?

--
Aditya.