Open prwhite opened 11 years ago
It would be nice to cache the results of node capability queries so they don't have to be done every time the library comes up.
Of course, this is worth benchmarking... if node discovery is not a bottleneck for startup, then it doesn't need to be optimized.
But, there will be other reasons to cache application state, such as user-defined node names, house maps, schedules, etc.
It would be nice to cache the results of node capability queries so they don't have to be done every time the library comes up.
Of course, this is worth benchmarking... if node discovery is not a bottleneck for startup, then it doesn't need to be optimized.
But, there will be other reasons to cache application state, such as user-defined node names, house maps, schedules, etc.