Thanks Damian for the information. I had just taken
ServerStoredAccountInfo as a class for storing account information and not
making any changes in it.
My progress regarding different protocols:
*For Jabber there was no existing code for either adddetail() or
*I have implemented both for Display Picture. In Jabber to change any detail
we need to upload a full VCard. That is even for a single change the whole
VCard needs to be uploaded. Because of this there is no real difference in
implementation for addDetail() or replaceDetail(). The only difference is in
prior checking conditions of both the functions.
*Another point is that in Jabber implementation, the function
isDetailCalssSupported() cant be used for addDetail() as the function only
returns values that were found by InfoRetreiver while parsing the VCard().
For in my case if initially the avatar was set to null then it will not be
returned as a supported class.
*Also as implemented in addDetail or replaceDetail of ICQ implementation,
there is no code for different supportedTypes. So I have used the
detailDisplayName as found in ServerStoredDetails for branching for
*There is no ServerStoredAccountInfo for MSN protocol.
*I will implement the classes ServerStoredAccountInfo and InfoRetreiver for
all functions related to Display Picture.
*ServerStoredAccountInfo is only implemented when using ICQ agent.
I have implemented the functions for Jabber protocol in
I have also attached the same file for review. All changes are in function
addDetail() and replaceDetail()
Will commit all changes including those in gui part as soon as our branch is
Next I will be implementing the same for MSN protocol after I getting
reviews for Jabber implementation.
Institute of Technology,
Banaras Hindu University,