3 causing error reply, that pep accepts as event. check message type/presence of error tag. |
3 causing error reply, that pep accepts as event. check message type/presence of error tag. |
4 * check input/output for validity, where applicable |
4 * check input/output for validity, where applicable |
5 * extract common code into one place |
5 * extract common code into one place |
6 * add avatar |
6 * add avatar |
7 * pep_avatar, avatar_cache, avatar, aavatar (separate) |
7 * pep_avatar, avatar_cache, avatar, aavatar (separate) |
8 * hook_avatar_metadata_in @ pep_avatar |
8 * in |
9 | hook_avatar_need_data_in (or symbol-resolved request) @ avatar_cache |
9 * !avatar-metadata-in @ pep_avatar |
10 V hook_avatar_data_in @ pep_avatar |
10 * symbol-resolved request @ avatar_cache |
11 hook_avatar_in @ avatar_cache |
11 * !avatar-data-in @ pep_avatar |
12 * (!!!) how to handle outgoing event? what and where should do what? |
12 * !avatar-in (file) @ avatar_cache |
|
13 * print, printaa @ avatar, aavatar |
|
14 * out |
|
15 * avatar_cache calculates hash and saves hash to cache(, links jid to hash?) |
|
16 * avatar_cache !avatar-data-out |
|
17 * pep_avatar sends data |
|
18 * pep_avatar reports error/notify of success (does static handler have node info?) |
|
19 * avatar_cache gets file from cache, calculates metadata, !avatar-metadata-out |
|
20 * pep_avatar sends metadata |
|
21 * pep_avatar reports error/(notify of success?) |
|
22 * avatar_cache (links jid to hash?) |
13 * handle url avatars (curl) |
23 * handle url avatars (curl) |
14 * report absence of avatar |
24 * report absence of avatar |
15 |
25 |