Change internal representation of UID about teddycloud HOT 3 OPEN

i can understand your impression. it might be right, maybe not. not sure.

We have the UID in different representation to be handled. As UID-string, as rUID-string as rUID bytes.
Quite a mix depending on what it's used for. That is also a bit pain for me.

And yeah, maybe uint64 might be the best choice plus some conversion routines back and forth.
If you could go through the code and check if it in the end gives cleaner code, it would be fine for me.

from teddycloud.

Both representations are used for different purposes, the one to compare and the one to identify physical files.
But I see no problem streamlining it into a a UID uint64 representation, as this could clean up the code a bit.

I currently don't see that this would fix the lower/uppercase problem, we check for path existence for an UID, not checking each file/dir.

from teddycloud.

The idea was that if you compare uint64 rather than strings you have no case anymore. But that might be easier said than done. Just looked at some code in handler_cloud.c and it seemed more complicated that it'd need to be. As stated previously, I'm not that deep into the code base and it might be a "Schnapsidee". I'll give it a try once I have some time.

from teddycloud.