Comment 1 by Loïc d'Anterroches, Nov 29, 2008

This is not as easy as one can think as different people can have 
different rights. For example, projects members can have access to 
the source but not normal users. This means we need to define the 
feeds as something like:

http://domain.tld/p/myproject/issues/feed/1234567abcdefg/

with 1234567abcdefg being a token allowing InDefero to find which 
user the request correspond, which cannot be forged and which can be 
reset if the user forward an email with the url to the wrong person.

It will mostlikely be a string containing the userid of the user + a 
hash based on the password in the db (to allow easy reset with 
password change) all obfuscated with a simple routine together with 
a control hash based on the secret_key of the current installation.

Side note, better to use the Atom protocol for the feeds.

Comment 2 by Loïc d'Anterroches, Dec 2, 2008

Comment 3 by Loïc d'Anterroches, Dec 2, 2008

Comment 4 by Loïc d'Anterroches, Dec 2, 2008

I have a basic version which is working. I am using the timeline 
principle, that is, each object which needs to be in the feed must 
have a feedFragment($request) method. This method must return an 
<entry> block like that:

<entry>
   <title>Commit 20971</title>
   <link href="
http://domain.com/p/indefero/source/commit/20971/"/>
   <id>
http://domain.com/p/indefero/source/commit/20971/</id>
   <updated>2008-12-02T13:22:01+01:00</updated>
   <content type="xhtml">
   <div xmlns="http://www.w3.org/1999/xhtml">
       Increased the size of the edition area of the 
       documentation pages.
   </div>
   </content>
</entry>

That way I can iterate over the timeline with a filter by type of 
objects (also depending on the user rights) and easily build the 
feed.

Comment 5 by Brice Maron, Dec 2, 2008

Nice!

It would be great to have a <link /> tag in all specific pages 
for the object.

Like a link for commits in the source tab,...