M. Ranganathan wrote: > On Wed, Aug 5, 2009 at 9:20 AM, Peter Fowler<[email protected]> wrote: >> >>> -----Original Message----- >>> From: [email protected] >>> [mailto:[email protected]] On Behalf Of >>> Tambrea Cosmin >>> Sent: Wednesday, August 05, 2009 7:22 AM >>> To: [email protected] >>> Subject: [sipX-dev] Discussion on "Allow users to upload a >>> picture to theirprofile" >>> >>> Hi, >>> >>> I have started today to investigate the issue XX-5536 - Allow >>> users to upload a picture to their profile. I have some >>> questions/proposals: >>> - I considered that the upload image option should appear on >>> user portal My Information page. I have designed the new UI >>> for this page( >>> http://track.sipfoundry.org/secure/attachment/20628/avatar.jpg); >>> - I believe we should store the uploaded images on server, >>> with the name generated from the user ID(using the hash >>> generating algorithm available on >>> http://en.gravatar.com/site/implement/java); >>> - I searched on sipx code and found that an image >>> service(InternalImageService) is already implemented and I >>> hope to use it for locating the avatar on server; >>> - I believe that it's not necessary to store any information >>> into DB about the relation between user and the image name, >>> because the image stored on server will have an unique name >>> generated by the hash algorithm; >>> - If this new avatar section would appear on user portal, >>> then it should be done using GWT(?); >>> - A resize of the image should be done if the image is too >>> big(should be resized to a few kB); >>> - What would be the location on server where the images >>> would be stored? >>> - I didn't exactly understand the Peter's comment: "The user >>> can/would use their XMPP based IM client (connected to >>> OpenFire) to manage their picture (Avatar). SipX should >>> access the same Avatar (file) for viewing/updating purposes. >>> ". Should this avatar be the same as the image used in XMPP? >>> >>> Thanks, >>> Cosmin. >>> _______________________________________________ >>> 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/ >>> >> One of the primary purposes of the Avatar would be to present it to the >> user's >> Friends' IM clients. The XMPP server (in our case, OpenFire) provides >> the avatarThat said - w >> To the IM client as part of a vCard. >> Conversely a user can update his/her Avatar via the IM client. This file >> Is then transmitted to OpenFire (via XMPP) and OpenFire stores it in its >> internal >> User database. So it may be better to have one location for the Avatar >> on the SipX box and >> That location may well be OpenFire user database. This approach may (or >> may not) apply to other >> Personal information such as cell phone, home phone etc.\ > > > Good point. I agree with the approach of storing the Avatar using openfire DB. >
That's not an option. Please read this again: http://permalink.gmane.org/gmane.comp.voip.sipx.devel/17663 Synchronizing the sipXconfig photo with OpenFire avatar is a good idea. It should be done by providing proper REST API (on sipXconfig side) and XML/RPC API on openfire side. But it's not something we are tackling now. D. _______________________________________________ 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/
