[coyotos-dev] Some comments on Coyotos Microkernel Specification
Jonathan S. Shapiro
shap at eros-os.org
Thu Dec 8 10:42:56 EST 2005
>I seems now understand why it have been implemented in this way. I still
>do not think that this is a good solution. This smells like premature
>optimization whithout thorough use case analysis and benchmarks.
30 years of experience isn't enough?
>A hash-based solution necessary has more collisions than interface name
>by the definition of what a hash function is. So the compression scheme
>based on hash is necessary loosy. So please do not use word
>"deterministic", because it simply is not. Deterministic compression
>scheme should have a deterministic decompression function.
In this domain, we shouldn't see more collisions. You are confusing "deterministic" with "invertible". Deterministic is sufficient here.
> [have] getTypeName() method that return alleged type name as string.
This is only useful for human consumption.
More to follow later.
More information about the coyotos-dev