generation number [name respawn count]

Post Reply
crosser
Posts: 18
Joined: Thu Apr 03, 2014 7:05 am
os: linux
Contact:

generation number [name respawn count]

Post by crosser »

May I suggest that the developers consider keeping a "generation number" of a record associated with a particular name, i.e. the number of times a "name_update" was issued for this name, and reporting it in the "result" along with the remaining time to live and transaction id?

That'd be useful for caching in general, and for producing the SOA record in particular.

Thanks.
Eugene; id/crosser

phelix
Posts: 1634
Joined: Thu Aug 18, 2011 6:59 am

Re: generation number [name respawn count]

Post by phelix »

Interesting idea. As long as we keep the full blockchain it can still easily be counted from name_history, though.
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

crosser
Posts: 18
Joined: Thu Apr 03, 2014 7:05 am
os: linux
Contact:

Re: generation number [name respawn count]

Post by crosser »

Yes, my suggestions is somewhat of a premature optimization.

However, for a DNS bridge (on which I am currently working), you potentially want the generation number on every query. Doing name_history instead of name_show looks like a waste.
Eugene; id/crosser

crosser
Posts: 18
Joined: Thu Apr 03, 2014 7:05 am
os: linux
Contact:

Re: generation number [name respawn count]

Post by crosser »

I realized that my suggested autoincremented counter does not solve the problem. If there is an "import" in a subdomain in the "map", and the object that is being imported changes, this will not be noticed unless you recursively resolve all subdomains in the zone. Which defeats the purpose of of the SOA in the first place.

For now, I am just using time in my bridge.
Eugene; id/crosser

Post Reply