← Back to team overview

acmeattic-devel team mailing list archive

Re: Components split up diagram

 

It looks like we are definitely on the same page!

On Wed, Jul 7, 2010 at 2:55 PM, Aditya Manthramurthy
<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.

IPC: When there is network, why IPC? This limits future scalability.

I've updated the webpage with my proposal of the design. (
http://www.nkarthiks.info/acmeattic/index.php?title=Implementation#Alternative_Design_Proposal).
I am just being more flexible with the design.

The web application has to perform many of the client actions such as
handling keys, perform diff's, handling sharing semantics, etc. Since this
is already implemented in the client, why not reuse the core in the webapp?


> --
> Aditya.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~acmeattic-devel<https://launchpad.net/%7Eacmeattic-devel>
> Post to     : acmeattic-devel@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~acmeattic-devel<https://launchpad.net/%7Eacmeattic-devel>
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Karthik

Follow ups

References