4.1.10.1 Avatar presentation for contacts

Starting the dialer (for the first time and subsequent times)

Dialer po uruchomieniu powinien wyslac do Webapi timestamp najnowszej zmiany znaleziony dla wszytskich vippie contacts. Tzn szukamy najnowsze ALC (avatar last change) jakie mamy zapisane.

Check method in webapi 4.1.10 Profile

ALC is sent to Webapi according to the method description. When you first start the dialer, we send the date 1900-01-01T00:00:00.

The procedure for checking whether there are avatars should be performed the first time you enter the Contacts Menu after starting the dialer.

After sending the request, the server returns the logins of clients whose avatars have changed since the time we specified. The timestamp of changes for each login (ALC) and information whether the file/avatar exists or not are also returned (it may happen that someone deletes their avatar).

A separate table should be created with the following fields, each record should be associated with a vippie login ID:

avatar_last_change

avatar_thumbnail_filename

avatar_filename

downloaded 0 or1

After the response from webapi, we enter a new ALC for each returned login and set downloaded to 0 if fs=1 (i.e. there is an avatar). If fs=0, we set downloaded=1 and if there is any avatar file assigned to this login, we must delete it.

Nastepnie nalezy uruchomic procedure pobierania avatarow (GET_AVATARS). Procedura powinna wywolywac metoda Get z webapi dla kazdego z loginow dla ktorego downloaded jest 0. Konczy sie gdy wszytskie 0 zostana zmeinione na 1.

IMPORTANT: when running this procedure, check whether it no longer works, i.e. set the GET_AVATARS flag and check its status when you try to run it. It is important that many procedures downloading avatars do not run at the same time.

Before starting the download, you must put NULL in the avatar filename and avatar_thumbnail_filename fields.

The Get function will download the thumbnail, it is important to send optional parameters w and h specifying the width and height. adjust them so that they look good in the contact list. after downloading, set downloaded=1 and enter the file name in the avatar_thumbnail_filename field, the name should be in the format (login)_thumbnail.jpg. The avatar_filename field becomes NULL.

When entering the profile view of a given contact, check whether the avatar_thumbnail_filename field is different from NULL and whether avatar_filename = NULL. for such a case, you should do Get without the w and h parameters to download the full-size avatar file. After downloading, enter the file name in the format (login)_avatar.jpg

If an error occurs during downloading, there is no Internet, etc., you should reconsider the procedure. e.g. check if there are any records with downloaded 0 every few minutes and try to download until successful, i.e. until all downloaded are 1.

 Storing Avatars 

We keep downloaded avatars locally assigned to a given login.

Avatars are to be shown:

1) in the Contacts list (thumbnails)

2) in the view of a given contact, we show them in a medium-sized window appropriate for a given platform.

WE DO NOT OVERWRITE AVATARS FROM THE NATIVE BOOK,, we only show our avatars in our application

If someone does not have an avatar in our application but has a native avatar, we show the native one.

Support for avatar change information via NOTIFY

When changing your avatar (and also when changing the status text), the dialer sends PUBLISH to the server, and the server, in turn, sends NOTIFY to each user/watcher.

the NOTE field in the NOTIFY message looks like this:

<note>

<alc>timestamp</alc>

<text> here is the text status.</text>

</note>

In the NOTE field we always send ALC and TEXT. If the date in ALC from NOTIFY for a given login is different from the date stored locally, you should follow the same procedure as when starting the dialer, i.e. you should send the latest ALC saved in the database to webapi (not the ALC from notify, the point is that the server can us to return more changes that somehow did not reach us). After receiving the Response, perform the actions as described above.

then you should check whether the GET AVATARS procedure is already working. If not, we'll start.

 New contact

When a new vippie contact(application contact) arrives (via SMS), you should perform the Check method in webapi. Instead of ts, you should provide the av parameter and the vippie login value for this contact. In response, we will receive ALC information and fs=1 if the avatar exists or fs=0 if there is no avatar. Accordingly, you should set downloaded=0 if fs=1 and insert ALC. Then run CHECK_AVATARS. If fs=0, then downloaded=1 and insert ALC