@Aaronontheweb have you read my message about Mongo2Go?
I think I could use my fork and provide a different database directory but then I need to include the dll and mongodb in the test repositories instead of the nuget pakage
Package
@Horusiath I would like to replace the custom serializer with the build in one from mongodb so that the user can customize how the events are serialized but this would also add a responsibility that he registered all his events before using a persistence actor. Is this ok or do you thing the plugin should handle this ?
@Silv3rcircl3 persistence plugins usually don't describe how payloads should be serialized (it's up to user to decide), however some of Akka.Persistence messages have defined proto-buff serialization - in this case custom payload is first serialized using custom/default serializer, but then it is treated as binary field of persistent enveloping message and serialized using proto-buf
if you want, you could provide your own MongoDb-oriented serializer, but it had to be configured for:
Akka.Persistence.Serialization.Snapshot, Akka.Persistenceto serialize snapshot envelopes (with content)Akka.Persistence.Serialization.IMessage, Akka.Persistenceto serialize journal message envelopes (also with content)
limitation is that serializer is expected to work with binary data
I don't know if mongodb driver exposes an API to send already binarized data through it
You mean a at least once delivery message for example? This would arrive as byte array in the payload property when I want to store it in the event journal?
I mean that when you're calling
IPersistentRepresentation serialization/deserialization, it has configured an explicit proto-buf message serializer
but maybe I'm blurring to much ;) I guess, that you want to serialize journal events/snapshots in such way, that their fields could be visible from mongo db engine perspective?
Exactly :-) actually I'm using the serializer that is provided by System.Serialization.FindSerialzerForType(IPersistentRepresentation) call toBinary and store the byte array as Payload in the JournalEntry mongodb
Now I want to store the PersistenceReprestation.Payload object directly without serialization
Ok, great ;-)I will add a section to the readme to be save
poisonous squirrel
can somebody point me to a doc that explains what to replace it with, i am using it as most of the actors have other dependencies
it says to use Props instead, but wouldn't that mean that i have to provide the dependencies directly rather than let the container do it?
sorry if it was asked/discussed before
is that the way to do it now? Context.ActorOf(Context.DI().Props<>)?
Hi guys! I have a question fot you) How can I set up Akka to perform this logic: 1. I want to have two equal actors subscribed to the EventBus, 2. When I put a new message to the EventBus, only the first free actor will recieve this message and the second will not?
you can not do that with the EventBus, EventBus will publish to all subscribers.. you could do a SmallestMailbox router with two actors, and let the router subscribe to the eventbus.. thats the closes you will get
@rogeralsing if we could settle on some decision about
BackoffSupervisor I could continue refucktoring of akka cluster sharding ;)
@tstojecki yup it is. The docs have been updated a few days ago. http://getakka.net/docs/Dependency%20injection
If there is anything unclear about it in the docs. Please let us know :)
@Danthar I think I remember the example "Example supervisor strategy" here: http://getakka.net/docs/concepts/supervision being out-of-date, I could be wrong though
thanks @danthar, i just read it and it looks very accurate...
somehow when googling it i kept landing on http://getakka.net/docs/DI%20Core
maybe there should be a link between the two just to clarify
i wish it had taken me to the doc you pointed me to
@chris-ray the supervision document is ok :)
@trbngr i would love to see a 1st class support of async/await too
i have used PipeTo and the contrib project for asyncActors
i know there were long debates about that, not trying to start another one :)
Yes.. Receive actor with async method preserves context
@Danthar: could you take a look at the Dependency Injection documentation regarding Child Actors? it is wrong. you can't use Context.DI().Props() with a lambda expression. there's only one accepting a type and a generic one without a parameter. would defeat the purpose of DI to provide one with a lambda that instantiates a class not using DI
i'm heading to bed myself now. so good night
