Serialising ASP.NET method calls for later execution (opens in new tab)

(johnnyreilly.com)

1 pointsjohnny_reilly1y ago2 comments

2 comments

> So how can we take a method call, serialise it, perhaps store it in a database, and then later rehydrate and execute?

Any messaging queue would be better. Yes it's easy to setup. No it doesn't require additional complexity (in fact, it's less complex than the proposed solution)

example: https://www.rabbitmq.com/tutorials/tutorial-one-dotnet#recei...

johnny_reillyOP1y ago

Queues are great; but it looks like you're trying to solve a different problem. In my own case, the aim was to store a function for delayed execution. That's slightly different from storing typical state. The interesting bit (hopefully) in here is serialising and deserialising function calls.

j / k navigate · click thread line to collapse

2 comments

bunbun691y ago

> So how can we take a method call, serialise it, perhaps store it in a database, and then later rehydrate and execute?

Any messaging queue would be better. Yes it's easy to setup. No it doesn't require additional complexity (in fact, it's less complex than the proposed solution)

example: https://www.rabbitmq.com/tutorials/tutorial-one-dotnet#recei...

johnny_reillyOP1y ago

j / k navigate · click thread line to collapse