acmeattic-devel team mailing list archive

[krishnan parthasarathi <krishnan.parthasarathi@xxxxxxxxx>]

Hi all,
You must have noticed the recent push by me into the main branch of
acme-attic.
Let me give a brief overview on what went in. From our earlier discussions
we
had decided to use the https protocol as our transport protocol. We are
currently using *django* as our middleware to handle the https requests[1].
You
can see the changes under the middleware directory in django_services.  We
had
also decided that we would need a message format for the protocol messages
that
the acme-attic client and server need to exchange for carrying out user's
commands.  We are currently using *thrift* for defining a serialization
format
for the protocol messages. The reason to use thrift is that it supports
bindings in most of the modern languages and hence these messages can be
processed in those languages. You can see the changes under the common
directory.  This is just a teaser introduction to the things that have gone
in.
I have added a README in each of the directories that are affected by the
changes. Those are again meant to give only introductory details.

[1] - django handles only http requests and looks like some extra work needs
to
 be done on top to get https transactions working with django. This needs
some
 looking up.

-- 
--Krishnan Parthasarathi