Re: Question about the sequential flag on create.

Nodes are maintained un-ordered on the server. A node can store any subnodes, not exclusively sequential nodes. If we added an ordering guarantee then then server would have to store the children sorted for every parent node. This is a problem for a few reasons; 1) in many cases you don't care

Re: Question about the sequential flag on create.

Hey Patrik! Thanks for the reply. I understand all the reasons that you posted above and totally agree that nodes should not be sorted since you then have to pay that overhead for every node, even though you might not need or want it. I just thought that it might be possible to create a sequential

Re: Question about the sequential flag on create.

the create is atomic. we just use a data structure that does not store the list of children in order. ben Erik Holstad wrote: Hey Patrik! Thanks for the reply. I understand all the reasons that you posted above and totally agree that nodes should not be sorted since you then have to pay that

Re: Question about the sequential flag on create.

Thanks Patrick!

Question about the sequential flag on create.

Hey! I have been playing around with the queue and barrier example found on the home page and have some questions about the code. First of all I had trouble getting the queue example to work since the code turns the sequence number into an int and then try to get information from it, missing out

Re: Question about the sequential flag on create.

Hi Mahadev! Thanks for the quick reply. Yeah, I saw that in the source, but was just curious why that is, since it is a part of an internal counter structure, right? Regards Erik