Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 29 2016 04:58

    Corwynt on master

    added MoinComponent.getSettings… 1.2.0 Merge remote-tracking branch 'o… (compare)

  • Aug 25 2016 17:04

    Corwynt on master

    Fixed readme examples Merge pull request #2 from amil… (compare)

  • Aug 25 2016 17:04
    Corwynt closed #2
  • Aug 25 2016 16:53
    amilajack opened #2
  • Aug 10 2016 09:37

    Corwynt on master

    Changed Readme. Re-added lost l… 1.1.3 (compare)

  • Aug 09 2016 14:29

    Corwynt on master

    Added the init flag. With this … 1.1.2 (compare)

  • Aug 09 2016 14:00

    Corwynt on master

    Added `moin` binary. Added the … 1.1.0 Added the init flag. With this … and 1 more (compare)

  • Jul 13 2016 08:49

    Corwynt on master

    Added Link to homepage Merge remote-tracking branch 'o… Added Link to homepage (compare)

  • Jul 13 2016 06:11

    Corwynt on master

    Add Gitter badge Merge pull request #1 from gitt… (compare)

  • Jul 13 2016 06:11
    Corwynt closed #1
  • Jul 12 2016 21:37

    Corwynt on master

    Initialization process changed (compare)

  • Jul 12 2016 21:33

    Corwynt on master

    Initialization process changed (compare)

  • Jul 12 2016 21:32

    Corwynt on master

    Initialization process changed (compare)

  • Jul 12 2016 21:30

    Corwynt on master

    Initialization process changed (compare)

  • Jul 12 2016 19:01
    gitter-badger opened #1
lius
@lius
hey guys!
A quick question about moin: it covers interprocess communication transparently, inside the same host and in different hosts?
Would be great a overview of how it works internally
Corwynt
@Corwynt
Hey @lius. in one moin instance the module „moin-event-system“ handles the communication between the services. The services run all in one node application.
The excecution of events works in two phases: collect and excecute
collect gathers all handlers which are fitting and returns a list of ids(in case of act only the best fitting handler and its score)
excecute takes a handler id and the event and excecutes the handler
when two or more moin instances are connected two each other, the collect phase is done internally on the emitting instance and is send through socket.io to the other moin instances.
the instances then do their own collect phase and the result is send back to the first instance
lius
@lius
thanks, @Corwynt !
Corwynt
@Corwynt
I hope this helps ^^ i have some graphics for it in my bachelor thesis. but i have to wait for the oral exam until i can make it public
lius
@lius
how disvery is done?
*discovery
nice
Corwynt
@Corwynt
with the bundled module it is just a client server architecture. the ip address to connect to can be set in the config.json file. But it is very easy to write an own module which handles the sending of events(e.g. over a messaging queue).
lius
@lius
ok
I know that the project really is lacking of documentation. i will try to work on it in the next weeks ^^
lius
@lius
I got it
the communication throught socket.io is nice, since it’s not require a central server to do that
would be good too if auto discovery is possible in this scenario
Corwynt
@Corwynt
The current implementation only allows one server. But i will have a look on how i can make the instances works as both. I only have to find a way to stop events running in circles.
lius
@lius
when reach a larger number of services, configuration in parameters make difficult to operate
Corwynt
@Corwynt
since the configuration of services is also an interchangable module it could be interchanged with a module which loads the settings from another datasource. If you have ideas on how to enhance the project just add a feature request on github.
lius
@lius
great!
Friedemann Stoffregen
@Donderda
staub wisch