Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 03:08
    hhko commented #4094
  • Dec 13 21:37
    Aaronontheweb commented #4085
  • Dec 13 20:28
    IgorFedchenko commented #4085
  • Dec 13 20:27
    IgorFedchenko commented #4085
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb milestoned #4096
  • Dec 13 15:38
    Aaronontheweb labeled #4096
  • Dec 13 15:38
    Aaronontheweb opened #4096
  • Dec 13 10:41
    peirens-bart opened #4095
  • Dec 13 08:37
    Aaronontheweb synchronize #4071
  • Dec 13 08:13
    jiyeongj opened #4094
  • Dec 12 15:42
    Aaronontheweb synchronize #4086
  • Dec 12 15:42
    Aaronontheweb closed #4083
  • Dec 12 15:42

    Aaronontheweb on dev

    Fix #4083 - Endpoint receive bu… (compare)

  • Dec 12 15:42
    Aaronontheweb closed #4089
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb labeled #4093
  • Dec 12 15:42
    Aaronontheweb opened #4093
  • Dec 12 14:20
    Aaronontheweb commented #4092
Maciek Misztal
@mmisztal1980
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 }
Arjen Smits
@Danthar
Akka.net is .net only. We dont have wire level compatibility with the JVM version. (yet) So im not sure thats actually a problem.
Jari Pennanen
@Ciantic
I have to look how the Scala version's HTTP layer works
it can be used from other languages
Arjen Smits
@Danthar
Not familiar with the framework. But im guessing it works because of the common well known protocol namely HTTP ?
Jari Pennanen
@Ciantic
@Danthar yes, but if you send Something.Greet, it must send the name of the item also
not only the json
Zetanova
@Zetanova
@Ciantic Newton Json serializer includes the type into the payload
But i dont know how u will conect to akka system with a differnt "languge" that cant reference akka.remote assembly
Jari Pennanen
@Ciantic
@Zetanova apparently I can't, but someday when .NET Akka supports HTTP it maybe possible
looking now how to "curl in to Akka.io"
Zetanova
@Zetanova
write an warpper
with WebAPI and singularR and hosted with owin or IIS