Re: [GNUnet-developers] Listing Egos

[Martin Schanzenbach]

Hi,

<rant>
I wondered that as well. Not only does every developer have to
"remember" what he is told on connect (i.e. create a data structure),
he is also supposed to update that data structure when there are
updates.
This is not how, for example, namestore works. Is there any technical
reason for this decision?

It seems to require (1) a lot of boilerplate management code when I
want to use identities and (2) inevitably lead to a lot of copy/paste
code and bugs. Now that I think of it I think my recent additions might
all use the service wrong, in that I do not sync my local identity list
(That I don't really want to keep but I have to since there is no list
API call and no, I do not want to create my own "list" call by
reconnecting as I would have to add a comment that says "Reconnect so
we get a list of egos") with identity service callbacks.

I mean, all consumers of this service will basically have to implement
similar data structures and react to the callbacks in the same way.
That sounds fishy. In fact, I noticed that since I have to manage all
identities in my DS anyway I never really use ego_lookup. There
literally is no use case for this API call at all as you would get your
lookup result in the connect callback. After that, I have all
identities in memory anyway...
</rant>

And I agree with zPlus: I don't want to manage identities. I want an
API that gives me an Ego by key or name or list all (just like
namestore). Maybe a callback for changes is necessary as well, just
like namestore, so I don't have to poll for updates. So unless there is
a technical limitation maybe at least harmonize namestore and identity
API?

Just my 2 cents
Martin

On Fri, 2016-01-22 at 13:24 +0100, Christian Grothoff wrote:
> If you just need it "once in a while", then just connect to the
> identity
> service when you need it, and close the connection once you are done.
> 
> On 01/22/2016 01:21 PM, zPlus wrote:
> > I do understand this, but to me it seems very convoluted to
> > implement
> > what is basically a complete identity manager (I have to handle all
> > add/remove/rename/etc. events), when all I want is just a list of
> > the
> > available pseudonyms every once in a while.
> > 
> > 
> > On Fri, 2016-01-22 at 12:51 +0100, Christian Grothoff wrote:
> > > 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.).
> > 
> > 
> > _______________________________________________
> > GNUnet-developers mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/gnunet-developers
> > 
> _______________________________________________
> GNUnet-developers mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnunet-developers