Improved Bridge (more inline with how node works)

[prologic]

No description provided.

[landscape-bot]

Repository health increased by 0.04% when pulling 03dac08 on improved-bridge into 53aebc8 on fix_bridge_cleanup.

• 1 new problem was found (including 0 errors and 0 code smells).
• 2 problems were fixed (including 0 errors and 2 code smells).

[prologic]

This changes the Bridge usage a bit:

• Removes implicit event traversal.
• Events are now explicitly sent to a subprocess.

Usage:

from __future__ import print_function

from os import getpid


from circuits import child, Event, Component


class hello(Event):
    """hello Event"""


class Child(Component):

    def hello(self):
        return "Hello from child with pid {0}".format(getpid())


class App(Component):

    def init(self):
        Child().start(process=True, link=self)

    def ready(self, *args):
        x = yield self.call(hello())
        yield print(x)

        y = yield self.call(child(hello()))
        yield print(y)

        raise SystemExit(0)

    def hello(self):
        return "Hello from parent with pid {0}".format(getpid())


App().run()

Output:

$ python test_bridge.py
Hello from parent with pid 814
Hello from child with pid 817

[landscape-bot]

Repository health increased by 0.04% when pulling 1f93989 on improved-bridge into 53aebc8 on fix_bridge_cleanup.

• 1 new problem was found (including 0 errors and 0 code smells).
• 4 problems were fixed (including 0 errors and 4 code smells).

[landscape-bot]

Repository health increased by 0.04% when pulling 584fdff on improved-bridge into 53aebc8 on fix_bridge_cleanup.

• 1 new problem was found (including 0 errors and 0 code smells).
• 4 problems were fixed (including 0 errors and 4 code smells).

[prologic]

This also works with multiple subprocesses:

Example:

from __future__ import print_function

from os import getpid


from circuits import child, Event, Component


class go(Event):
    """go Event"""


class hello(Event):
    """hello Event"""


class Child(Component):

    def hello(self):
        return "Hello from child with pid {0}".format(getpid())


class App(Component):

    def init(self):
        self.counter = 0
        self.child1 = Child().start(process=True, link=self)
        self.child2 = Child().start(process=True, link=self)

    def ready(self, *args):
        self.counter += 1
        if self.counter < 2:
            return
        self.fire(go())

    def go(self):
        x = yield self.call(hello())
        yield print(x)

        y = yield self.call(child(hello()), self.child1[1].channel)
        yield print(y)

        z = yield self.call(child(hello()), self.child2[1].channel)
        yield print(z)

        raise SystemExit(0)

    def hello(self):
        return "Hello from parent with pid {0}".format(getpid())


App().run()

Output:

$ python examples/hello_bridge.py
Hello from parent with pid 1733
Hello from child with pid 1736
Hello from child with pid 1737

[landscape-bot]

Repository health increased by 0.06% when pulling 8430985 on improved-bridge into 53aebc8 on fix_bridge_cleanup.

• 1 new problem was found (including 0 errors and 0 code smells).
• 4 problems were fixed (including 0 errors and 4 code smells).

[prologic]

/cc @spaceone @treemo @circuits/developers Need some input/feedback on this one :) These are breaking API changes on Bridge; but I don't think it's ever been used very much likely because of it's poor design/API in the first place :) I think it's a lot more useful now!

[landscape-bot]

Repository health increased by 0.06% when pulling e5c6aba on improved-bridge into fe2e7e0 on bug-fix#51.

• 1 new problem was found (including 0 errors and 0 code smells).
• 4 problems were fixed (including 0 errors and 4 code smells).

[prologic]

bump!

[prologic]

I want to get this merged in pretty quckly so speak y'all :) I have a use-case for this improved bridge in oss6/statico#12

[treemo]

@prologic I never use the bridge (I use node for dispatch the events on process / host)

[prologic]

@treemo Yeah that's cool! I tried to modify the bridge such that it has a very similar API and usage to Node :) What do you think anyway?

[spaceone]

I'll give my feedback in the evening (in german time zone).

[landscape-bot]

Repository health increased by 0.09% when pulling 5449fd3 on improved-bridge into fe2e7e0 on bug-fix#51.

• 1 new problem was found (including 0 errors and 0 code smells).
• 4 problems were fixed (including 0 errors and 4 code smells).

[spaceone]

I think the change is really nice, i like explicity... But I don't like the event name child. I currently can't think of which name suits better.

[prologic]

The reason I called it child() was the following connotations:

• Let's fire a remote event foo to host:port
• Let's fire a child event foo to uuid

[prologic]

@ALL Okay so we could call the event ipc() if that makes more sense?

Was just thinking about this; you could also message the parent, not just the child. For example in pingpong.py

[prologic]

Bump :)

Also see: https://gist.github.com/prologic/7bb5bbcecfb79bfdc841

Just playing around here... Could turn into something more concrete!

[landscape-bot]

Repository health increased by 0.09% when pulling cd83397 on improved-bridge into fe2e7e0 on bug-fix#51.

• 1 new problem was found (including 0 errors and 0 code smells).
• 4 problems were fixed (including 0 errors and 4 code smells).

[prologic]

bump

[landscape-bot]

Repository health increased by 0.12% when pulling cd83397 on improved-bridge into 68a6a8d on master.

• 1 new problem was found (including 0 errors and 0 code smells).
• 6 problems were fixed (including 1 error and 4 code smells).

[prologic]

I'm going to rename the event to ipc() and merge this!