shindig-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Achala Chathuranga Aponso <>
Subject Re: creating relationships (createPerson SPI feature)
Date Sat, 03 Dec 2011 06:56:32 GMT

I think creating relationships is a part of opensocial 2.0.1 specification,
but still it is not supported in shindig. Currently shindig has given the
chance to implement the relationship process according to the choice of the
social container implementer.

I think relationships can be managed by the owner and viewer concept. From
the *getDisplayName () of the Person interface*  , you can find the display
name of profiles. You have to get the display name of the logged in user.
if the logged in user is visiting another user s profile. The logged in
user becomes the viewer and the other one becomes the owner. From those
Display names it is possible to create relationship requests. (when the
owner logs in he/she can see the friend request which is pending approval).
Correct me if i am wrong. :)


On Fri, Dec 2, 2011 at 10:55 PM, Goix Laurent Walter <> wrote:

> Hello,
> I apologize if I am using the wrong list for this.
> I would like to create relationships (e.g. start following another user)
> using the People Service. However it seems that neither the PHP nor the
> Java implementation supports it for the time being (the PersonService
> interface only has support for getPerson & getPeople)
> I couldn't find any reference to this in the current issues. Could you
> point me to the appropriate issue if any, or tell me whether this is in
> roadmap?
> Thanks
> walter
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle
> persone indicate. La diffusione, copia o qualsiasi altra azione derivante
> dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora
> abbiate ricevuto questo documento per errore siete cortesemente pregati di
> darne immediata comunicazione al mittente e di provvedere alla sua
> distruzione, Grazie.
> This e-mail and any attachments is confidential and may contain privileged
> information intended for the addressee(s) only. Dissemination, copying,
> printing or use by anybody else is unauthorised. If you are not the
> intended recipient, please delete this message and any attachments and
> advise the sender by return e-mail, Thanks.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message