Am 01.05.2016 um 22:27 schrieb Rene Gollent:
On Sun, May 1, 2016 at 3:04 PM, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
In my BLooper equivalent, you could add message channels to the looper fromThat would be cool, though I have to admit that my current familiarity
which it would receive its messages.
We could do something similar if we want; the registrar could act as the
first time router, connecting the clients (if both agree), and then let them
talk directly to one another.
with the internals of both the registrar and the respective aspects of
BLooper and friends isn't strong enough that I'd be confident in
making the necessary changes for all of that possible without
considerably more research :-) Doubly so given how critical those
components are to basic functionality of pretty much everything else.
Initially I just wanted a convenient way for an app with a local and
remote component to communicate using messages across a socket without
having to worry much about all the low level details.
BTW now that I think of it: isn't mmlr's remote desktop solution also basedI honestly have no clue of the latter's implementation I'm afraid.
on sending messages over the network? Maybe one could unite the two (sorry
for getting this idea so late).
