I load all the names at once. If this ever became a problem I'd segment them with bloom filters or something like that.
Note that in my applications the names are not known at runtime because comparing the guids is sufficient and these drop downs are not shown to the user but only the designer.
Were I employing this system in a more distributed fashion I might reconsider packing the names with guids understanding of them to be frozen after build.
I'm also considering a method to allow an engineer to limit the scope of key so that the designer is presented with a subset and not aall of the key options when setting the value.
Note that in my applications the names are not known at runtime because comparing the guids is sufficient and these drop downs are not shown to the user but only the designer.
Were I employing this system in a more distributed fashion I might reconsider packing the names with guids understanding of them to be frozen after build.
I'm also considering a method to allow an engineer to limit the scope of key so that the designer is presented with a subset and not aall of the key options when setting the value.