Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memory handles with status 'local data' and status 'for networking' #26

Open
divanchykhin opened this issue Oct 23, 2015 · 0 comments
Open

Comments

@divanchykhin
Copy link
Contributor

Currently we, by-fact, have only the second type which assumes reading by parsers and writing consecutively and somehow formatted, or, at least, ordered (to be parsed then); respectively, request and response parts make sense, etc. Data organized in this way is good for sending over network.
The other possible type is for storing/reading local data (for instance, locally defined structures). In this case reading/writing data between local buffers (such as structure on stack) and memory behind a handle is a typical operation; respectively, memory behind a handle is considered as just one block.
Despite internals operations over handles of the above two different types are different, and handles must have an indicator 9a flag) to which type they are related (with respective checks, etc)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant