On 4/20/2010 6:21 PM, Nair, Arjun (Arjun) wrote:
> My proposed solution for this issue [1]:
>
> 1. SipXopenfire will provide an XML-RPC interface that SipXconfig can call,
> whenever there is a change in a user's contact information.
>
> 2. Add an "Update Avatar" button in the user portal, which will allow the
> user to ask SipXopenfire to reload the Gravatar image. The implementation
> again takes form of an XML-RPC call from sipXconfig to sipXopenfire.
>
> I talked with Jason about this, and he was thinking of implementing a more
> general subscribe/notify XML-RPC framework, that could be reused by other
> components as well. I am not sure whether this is achievable in the 4.2.1
> timeframe. Should we push this into 4.3 or shall we go with the first
> solution?
>
> Arjun
>
> [1] http://track.sipfoundry.org/browse/XX-7894
> _______________________________________________
> sipx-dev mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
> sipXecs IP PBX -- http://www.sipfoundry.org/
>
+1 with your approach.. the subscribe/notify maybe better however we
can't take that for 4.2.1.
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
