Hi to everybody,
This is the third part of my blog about using persisntent classes as a quick tool for generating query classes and convenient reusing of them.
This is the beginning:
Part 1:
Persistent classes: revival of a spirit. Query by range.
and part 2:
Persistent classes: single get( ) method instead of multiple get_xxx() methods calls
Using this query class I figured out that in the case when we use the same request twice, we do the selection every time.
To improve the performance we need to create some buffer for retrieving previously selected requests.
So what we have as incoming parameters: request that is represented by a structure of any type and agent class.
To solve this abstract task I decided to use serialization technique again.
To be honest this is the first time I applied such a logic based on serialization and checksum calculation.
Has anyone used similar methods for generic hashing of anything? What is your opinion about overall performance: frequently called transormations and checksum calculations.
Thanks.
The full example you can find here: ZCL_OS_API
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
5 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |