Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:21
    Ralf1108 edited #3933
  • 14:17
    Ralf1108 opened #3933
  • 12:57
    Aaronontheweb commented #3904
  • 12:15
    Aaronontheweb synchronize #3927
  • 11:21
    Zetanova synchronize #3916
  • 08:35

    Aaronontheweb on dev

    Fix build script to be able to … (compare)

  • 08:35
    Aaronontheweb closed #3924
  • 08:28
    Aaronontheweb synchronize #3927
  • 08:28
    Aaronontheweb synchronize #3924
  • 08:28

    Aaronontheweb on dev

    added updated Windows Release p… Merge pull request #3869 from A… Fixed Akka.Remote.ResendUnfulfi… and 6 more (compare)

  • 08:28
    Aaronontheweb closed #3932
  • 08:22
    Aaronontheweb opened #3932
  • 08:16

    Aaronontheweb on 1.3.15

    (compare)

  • 08:14

    Aaronontheweb on master

    Fixed Akka.Remote.ResendUnfulfi… added v1.4.0-beta2 release note… added Akka.NET v1.3.15 release … and 2 more (compare)

  • 08:14
    Aaronontheweb closed #3931
  • 08:11
    Aaronontheweb synchronize #3931
  • 07:59
    Aaronontheweb commented #3905
  • 07:58
    Aaronontheweb edited #3931
  • 07:57
    Aaronontheweb commented #3889
  • 07:54
    Aaronontheweb synchronize #3931
Zetanova
@Zetanova
of course Context is somethign u will need
Jari Pennanen
@Ciantic
shouldn't it check the type?
Zetanova
@Zetanova
and IActorRef
Jari Pennanen
@Ciantic
I mean the fields
not the type name, which might not be available
Maciek Misztal
@mmisztal1980
good morning
anyone know if Akka.Remote supports port sharing?
Zetanova
@Zetanova
unlikly
Maciek Misztal
@mmisztal1980
my scenario is : attempt to run multiple lighthouse instances in a servicefarbric cluster - the local cluster has 5 virtual nodes, but they share the same physical host - so I was curious, if I can get it up and running that way. Apparently the SF communication listeners need to support port sharing :/
Zetanova
@Zetanova
i am not 100% sure, but for port sharing u need native support in the plattform to route the request to the proper process
like http.sys
Maciek Misztal
@mmisztal1980
seems that there's a port sharing service available https://msdn.microsoft.com/en-us/library/aa395195(v=vs.110).aspx
and it's being used in WCF
Zetanova
@Zetanova
yes, WCF
its SOAP
Jari Pennanen
@Ciantic
namespace ConsoleApplication11
{
    [ResultMatches("MyCompany.OtherAssembly.Greet")]
    public interface IGreet
    {
        public string Who { get; set; }
    }

    public class GreetingActor : ReceiveActor
    {
        public GreetingActor()
        {
            Receive<IGreet>(greet => Console.WriteLine("Hello {0}", greet.Who));
        }
    }
}
I wonder would that work
having own attribute there
which did the "connection"
then I would only need to agree on that string
and not link the assemblies
Zetanova
@Zetanova
?
and how does the message implementation looks like?
Jari Pennanen
@Ciantic
sending part?
Zetanova
@Zetanova
the message implementation is usualy put in a shared assembly
and dont realy need link to akka
you have then
Jari Pennanen
@Ciantic
yes but I wanted to have one without shared message implementation
Zetanova
@Zetanova
MyClient.dll
MyBase.dll
MySystem.dll
yes it can work, but its slow and very error prone
Vagif Abilov
@object
@Horusiath PR is submitted with clarification in PR comment.
Jeff Cyr
@JeffCyr
@mmisztal1980 When you run multiple service fabric node on the same physical host, the service endpoint's port is not shared, all service instance will be assigned a different private port that is retrievable through the service endpoint
Zetanova
@Zetanova
@Ciantic its a realy good idea to imeplement the messages in a shared assembly. It is basicly the contract definition without it you can pass JSON strings around, that would be even better then the interfaces
Maciek Misztal
@mmisztal1980
@JeffCyr Hi Jeff, can you point me to some material on this matter please?
Arjen Smits
@Danthar
@Ciantic What if you deploy multiple actors which "implement" the same interface ? (because your using a router/pool) How would your glue code handle that ?
Jari Pennanen
@Ciantic
@Danthar I haven't really thought this out, but I just find the idea that my listener need not to agree on one message assembly intriguing, it would allow me to write e.g. user service, and if I don't update my listeners they still work if their message fields matches with it
it is more error prone yes
but the listener could be even in different language
they just agree that with this string, I get this json
Arjen Smits
@Danthar
what is the role of your listener ? Where does it sit in your architecture ?
Jari Pennanen
@Ciantic
well the listnere need to be able to talk back in that example
e.g. "ResetPassword"
Arjen Smits
@Danthar
Ok, well because it sounds to me what your looking for is an "magic" solution to API versioning.
Jari Pennanen
@Ciantic
well, if the listener is in different language, it couldn't be bound to as
shared message assembly
it has to agree like string "MyCompany.OtherAssembly.Greet" matches with { Greet: string }
{ Who: string }