<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Il 07/30/2013 10:38 AM, Mitar ha
scritto:<br>
</div>
<blockquote cite="mid:51F77B78.9040805@tnode.com" type="cite">
<pre wrap="">Hi!
Nice stuff. :-)
Is REST interface django-tastypie based?
If I understand correctly, you pull changes? The last change always wins?</pre>
</blockquote>
<br>
Changes might be also pushed. It depends on how the synchronizer
class handles it.<br>
<br>
New custom synchronizers can be written and added to the available
synchronizers.<br>
<br>
A layer might be flagged as "external", and have "Nodewatcher" as
custom Synchronizer, and might continously synchronize with
Nodewatcher, for example.<br>
<br>
<blockquote cite="mid:51F77B78.9040805@tnode.com" type="cite">
<blockquote type="cite">
<pre wrap="">And hey, I started thinking there cannot be real interoperability
without the interoperable applications doing a kind of federated
authentication system with oauth or something.
Think about it.
</pre>
</blockquote>
<pre wrap="">
I am not sure if authentication itself is needed, but definitely systems
have to be able to create external accounts. So if I sync with you and
you have a node owned by user "foobar", I just have to create that user
in my system as well, but there is no need that user would be really
able to authenticate through my system, only a user object is needed.
The more serious issue is username conflicts between systems. We might
simply solve that by all external usernames to be mapped to something
like <a class="moz-txt-link-abbreviated" href="mailto:username@external-source-domain.com">username@external-source-domain.com</a> usernames.
With custom user classes in Django 1.5 this is probably easily done.
But you are right, for interoperability we should define user object
schema as well. At least username structure. I propose
<username>@<authentication-domain>, where local authentication domain
can use only username portion to authenticate.
We might even define a common Django authentication app for that. :-)
</pre>
</blockquote>
<br>
Maybe easier start thinking about it when we start doing it.<br>
<br>
<div class="moz-signature"><br>
<b>Federico Capoano</b><br>
Web Designer & Web Developer<br>
Portfolio/Blog: <a href="http://nemesisdesign.net">nemesisdesign.net</a><br>
Twitter: <a href="http://twitter.com/nemesisdesign/">@nemesisdesign</a><br>
PGP Key ID: 308BD46E</div>
</body>
</html>