Allow plugins to use PRIVATE memory instead of SHARED on requests #2086
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
svcMapProcessMemoryEx
svc so that it takes an extra flags argument. This change was made in a way that shouldn't break existing plugins or applications.MAPEXFLAGS_PRIVATE
flag, which maps the specified memory asPRIVATE
instead ofSHARED
.PRIVATE
memory instead ofSHARED
with a flag in the.3gx
header. This allows plugins to use socket and http services without additional hacks.