-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Contribution idea: Add support for Bond/Avro/other serialization #37
Comments
That sounds lovely. |
I'll add Simple Binary Encoding here too as it's used in low-latency financial Trading and may prove to be useful. This is like a continuation to the Codeplex thread where I ditched some haphazard ideas (I blame myself for not being able to engage in more thoroughly currently, but maybe sharing these is better than not). This touches upon #38 as in Codeplex there's a link to MBrace and code serialization which may be a useful idea. <edit: I noticed the Bing team has released a library to pool MemoryStream objects to improve performance. I see there's only one place where Perhaps this is interesting in the larger serialization context and when taking a look at ByteArrayBuilder and BufferPool and thinking if there are places that could make use of |
missing links: |
Looks like that was implemented via #953? |
@gabikliot As far as I see, that is the case. |
Yes, the generic solution that @Carlm-MS put together also covers non-Bond cases. |
…otnet#37) * Revamped transaction configuration to use type names. Silo setup using new config to register classes in DI. Silo defaults to InCluster type for Transactions with MemoryStorageLog. Fix TrasactionLog filename type. * Address feedback. * Address feedback: revert Silo whitespace changes, modify tx config ToString output. * Removed unneeded TypeName configuration values. * Apply null coalescing in config log.
PR Revamped TransactionConfiguration, DI enable TX class instantiation. dotnet#37 broke almost all of the transaction tests. This gets them working again.
One way to support Bond is to allow to use it optionally in addition to the built-in Orleans-generated serializers, similar to custom serializers. That way code that already uses Bond could work with Orleans.
The solution will probably need to add a message header to indicate serializer used
Will be less automatic than the built-in option but compatible with non-.NET clients
Explore other ways to use Bond.
The text was updated successfully, but these errors were encountered: