Brian, Inga, On 08/27, Gix, Brian wrote: > > The address part is useful when application would like to talk to its > > own node's Config or Health Server. > > (...) > I think I am OK with this... It is hard to make the argument that > this would be an information leak when the information has been > revealed before. And certain nodes (if they are authorized) need to be > able to talk to their own config servers. Ack. > > As for sequence number part (...) I would like to make it writable > > (increment-only) to enable address reuse, but as this stage I'm > > still looking for a way to implement this without causing a race > > condition, so I left it readonly for now. > > This is where I start to see actual danger, and difficulty when > considering the NVM system is "pre-reserving" sequence numbers to > prevent NVM thrashing during heavy use. In the spirit of keeping an > API as small as possible, giving applications the ability to adjust > the SeqNum (even in the legal direction) should have a rock solid > justification. Ok, fair enough. I'm gonna drop this property in v2. regards -- Michał Lowas-Rzechonek <michal.lowas-rzechonek@xxxxxxxxxxx> Silvair http://silvair.com Jasnogórska 44, 31-358 Krakow, POLAND
