Quantcast
Channel: ActorFx Source Code Rss Feed
Browsing all 121 articles
Browse latest View live

Source code checked in, #85441

1) Partitioning support: We can now exploit fabric service partitions. This lets us group together actors onto fewer service instances instead of creating a unique service instance for every actor,...

View Article



Source code checked in, #85451

Added support for Python actor methods. Also changed FabricActorClient.AddMethod and IActorState.AddMethod to accept a SupportedLanguages enum value rather than an integer. These are only called from...

View Article

Source code checked in, #85471

Overly-aggressive preconditions.

View Article

Source code checked in, #85507

Allows us to launch ActorFx applications on Azure, including the gateway app. The initial launching of the actor runtime cluster to Azure is, sadly, still unsupported. So these changes will be of some...

View Article

Source code checked in, #85618

Adding in partitioning support to IActorProxy. Now an actor method can create and call a partitioned actor. Fixing a stress bug involving our assembly resolve event. There's a subtle race between it...

View Article


Source code checked in, #85634

Added IronPython.Modules.dll lib and properly plumbed it through. This was missing from our initial Python support. I also changed some "dumb" ActorServiceResult serialization to "smart"...

View Article

Source code checked in, #85683

Removing a dependency on System.Numerics, for portable library compliance. The Actor Runtime was communicating errors about a primary no longer being the primary in a weird way. We were detecting this...

View Article

Source code checked in, #85684

Updating Actor Runtime libraries to have fewer dependencies.

View Article


Source code checked in, #85685

Removing needless System.Numerics dependency.

View Article


Source code checked in, #85686

Removing needless System.Numerics dependency.

View Article

Source code checked in, #85720

Refactoring to support factoring into client & server libraries. This makes future changes to use portable libraries smaller. Fixed up a number of build warnings too.

View Article

Source code checked in, #85791

Portable Library work 1) Converted the GroceryItem assembly to a .NET portable library. I needed to include a workaround for serialization - we are using a custom SerializableAttribute to work to get...

View Article

Source code checked in, #85792

Updating to JSON.Net version 5.0.6 * Modest serialization perf improvements * BigInteger serialization support

View Article


Source code checked in, #85948

"Pure JSON" changes Removed the .NET type from our JSON serialization streams. As a result, we're tracking JSON objects on the actor instead of .NET objects. This should improve our multi-platform...

View Article

Source code checked in, #85962

Made some changes that allow our actor gateway to run standalone in a local cluster. (Just run it from the command line with the argument "-standalone".) This should allow us to more thoroughly test...

View Article


Source code checked in, #86116

Now explicitly ordering the "length" byte transmitted during actor communications. Also did a general refactoring and streamlining of our low-level communication code.

View Article

Source code checked in, #86134

Refactoring for portable library work. Creating an ActorClient base class to subsume the functionality of FabricActorClient. Allows clients like CloudList<T> to not directly depend on certain...

View Article


Source code checked in, #86137

When awaiting in client-sensitive areas, don't rerun our networking-specific continuations on the UI thread.

View Article

Source code checked in, #86139

Add in a call to Flush in our NetworkHelpers code in just the right place. Added some plumbing to our actor gateway app so we can test it running locally against locally-deployed clusters. Our actor...

View Article

Source code checked in, #86145

Our Gateway app hit an exception a few times. It prints out the exception message, but not where it came from. Let's include the exception stack trace in the log so we have a better chance at fixing it.

View Article
Browsing all 121 articles
Browse latest View live




Latest Images