docs: describe GSB

[dopiera]

This change is 

[nieznanysprawiciel]

Reviewable status: 0 of 1 files reviewed, 4 unresolved discussions (waiting on @dopiera)

---

arch-snapshot/arch.md line 569 at r1 (raw file):

like [Windows
DCOM](https://en.wikipedia.org/wiki/Distributed_Component_Object_Model),
[CORBA](https://en.wikipedia.org/wiki/CORBA), and

Those links are good as an intuition at most when someone knows those technologies. But as a replacement for description they are rather poor, because they talk about completely different things :(

But let's leave this, because we are short on time anyway

---

arch-snapshot/arch.md line 582 at r1 (raw file):

  by paths composed of segments separated by a '/' sign. Components are
  responsible not just for a single path but for all paths that share a
  certain prefix. This design allows the path itself to carry additional

This is not true, at most it is only naming convention. In general you bind to GSB handlers to specific message on specific path. You are allowed to bind on prefix, but it is rather exception then rule, used only in net. And in this case you get untyped messages.

You are allowed to bind on any path even on prefix that by convention belongs to certain module.

Suggestion:

  Components are responsible not just for a single path but for all paths that share a
  certain prefix. This design allows the path itself to carry additional

---

arch-snapshot/arch.md line 588 at r1 (raw file):

* **Absence of remote service concepts**: GSB does not distinguish between
  local and remote services. Instead, a dedicated component, called **Net**,

Maybe link to specific chapter?

---

arch-snapshot/arch.md line 591 at r1 (raw file):

  is responsible for forwarding traffic to remote targets. The target’s
  address is specified within the path, and the Net component uses this
  address to direct the payload to the appropriate remote destination. It then

Maybe link to chapter about GSB prefix translation

[dopiera]

Reviewable status: 0 of 1 files reviewed, 4 unresolved discussions (waiting on @nieznanysprawiciel)

---

arch-snapshot/arch.md line 569 at r1 (raw file):

Previously, nieznanysprawiciel wrote…

Those links are good as an intuition at most when someone knows those technologies. But as a replacement for description they are rather poor, because they talk about completely different things :(

But let's leave this, because we are short on time anyway

Added some quick explanation.

---

arch-snapshot/arch.md line 582 at r1 (raw file):

Previously, nieznanysprawiciel wrote…

This is not true, at most it is only naming convention. In general you bind to GSB handlers to specific message on specific path. You are allowed to bind on prefix, but it is rather exception then rule, used only in net. And in this case you get untyped messages.

You are allowed to bind on any path even on prefix that by convention belongs to certain module.

Done.

---

arch-snapshot/arch.md line 588 at r1 (raw file):

Previously, nieznanysprawiciel wrote…

Maybe link to specific chapter?

Done.

---

arch-snapshot/arch.md line 591 at r1 (raw file):

Previously, nieznanysprawiciel wrote…

Maybe link to chapter about GSB prefix translation

Done.

[nieznanysprawiciel]

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @dopiera)

---

arch-snapshot/arch.md line 582 at r1 (raw file):

Previously, dopiera (Marek Dopiera) wrote…

Done.

hmmm, I have concerns, but let's leave it