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

Support for large payloads. #7

Closed
michaelstaib opened this issue Mar 28, 2018 · 1 comment
Closed

Support for large payloads. #7

michaelstaib opened this issue Mar 28, 2018 · 1 comment

Comments

@michaelstaib
Copy link
Member

The current generator will only accept value types and string as payloads to be compliant with etw. There are cases were customers still want to generate an event source with custom objects for which they handle the payload serialisation in an nonevent method.

The template info file should define which types are accepted by a template. Moreover, a template should explicitly in- or exclude types or work with wildcards.

@michaelstaib michaelstaib added this to the Version 1.1 milestone Mar 28, 2018
@michaelstaib michaelstaib changed the title Support for large payload handling. Support for large payloads. Mar 29, 2018
@michaelstaib
Copy link
Member Author

I think for the first version we will have just a simple bool switch in the template settings file "allowLargePayloads". The switch default is false in order to not affect existing templates.

If large payloads are disabled we will throw an exception like we do now. If large payloads are enabled the generator can use new metadata provided to the generator model to generate special code that handles large payloads.

We should add another cc template that shows how large payload handling could be implemented.

@michaelstaib michaelstaib closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant