You're confused about how identity uses the callback. It does NOT just give you the list of identities once upon connect, but it keeps you up-to-date as long as the connection is up. So you don't need to re-start the application or connection to reflect identity changes: you will always have the latest status if you process the various cb-events (there are arguments that tell you about add/remove/rename/etc.).
On 01/22/2016 12:31 PM, zPlus wrote: > Could anybody please add a GNUNET_IDENTITY_list function to the identity > service? > > I believe it will be very useful for applications that are supposed to > run for a long time (eg. gnunet-gtk) instead of returning immediately > (eg. gnunet-identity). For example when I ask gnunet-gtk to publish a > new file, it could use this function to let me choose a pseudonym and > avoid restarting the application to reflect identity changes. > > > On Fri, 2016-01-22 at 11:37 +0100, Christian Grothoff wrote: >> Not really, you're supposed to know what information you'll need in your >> process and keep it around ;-). Theoretically, you could connect >> *again*, but that's not how you should do this. > > > _______________________________________________ > GNUnet-developers mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnunet-developers >
0xE29FC3CC.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
