On Mon, Jan 24, 2011 at 11:28 AM, Luciano Resende <luckbr1...@gmail.com>wrote:

> On Sun, Jan 23, 2011 at 9:49 PM, Sinthuja Rajendran
> <r2sinth...@hotmail.com> wrote:
> >
> >
> >> It's open for discussion, but one approach could be that we start
> >> migrating pieces of what we have to the REST branch, and we then make
> >> it TRUNK (moving current trunk to a branch or something)
> >>
> >> But please, feel free to suggest new items to the roadmap, and
> >> different approaches for implementing it.
> >>
> >> Thoughts ?
> >
> > I'm currently going through the source code, and in the mean while I
> > thought to share some of my ideas.
> >
> >
> >
> > I hope making the PhotArk more interactive way among the users will be
> > another good feature.
> >
> >
> >
> > - When the users have been tagged or added for some user groups can send
> >  a notifications via a
> >
> > e-mail as other social web sites, this alerts the users and increase the
> >  flexibility too.
>

(1)


> >
> >
>
> I'd be cautions about flooding somebody's e-mail with tons of
> notifications. Maybe an option to workaround this is to expose photo
> feeds with recent added photos, modified albums, tags, etc and users
> in general can subscribe based on their preference.
>

+1 for having user preferences.


>
> >
> > - And also we can add the the commenting functionality for the albums.
>
(2)

I believe (1) and (2) are part of OpenSocial integration (User activities
and messages).
Some details can be found at [2]-[4]

[1]
http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/REST-API.html
[2]
http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/REST-API.html#rfc.section.3.4
[3]
http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/REST-API.html#rfc.section.7.3
[4]
http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/REST-API.html#rfc.section.10


Thanks,
Umashanthi




> >
>
> +1
>
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

Reply via email to