Contents

# Architecture
Flok uses a server/client architecture and has one two-endpoint communication channel that uses an extremely efficient pipelined messaging protocol.  See [Messaging](./messaging.md) for details.

The communications interface is divided up into two parts; interfaces (`if_*`) and interrupts (`int_*`).  Interfaces are going from the flok server to the client.  Interrupts are from the client to the flok server. There is only one real interface and only one real interrupt, these are `int_dispatch` and `if_dispatch`.  All the other interrupts and interfaces are `virtual` as in they are decoded via the flok server `int_dispatch` or for each platform, `if_dispatch` decodes their messages.

![](./images/flok_arch.png)

Version data entries

85 entries across 85 versions & 1 rubygems

Version	Path
flok-0.0.105	docs/architecture.md
flok-0.0.103	docs/architecture.md
flok-0.0.102	docs/architecture.md
flok-0.0.101	docs/architecture.md
flok-0.0.100	docs/architecture.md
flok-0.0.99	docs/architecture.md
flok-0.0.98	docs/architecture.md
flok-0.0.97	docs/architecture.md
flok-0.0.96	docs/architecture.md
flok-0.0.95	docs/architecture.md
flok-0.0.94	docs/architecture.md
flok-0.0.93	docs/architecture.md
flok-0.0.92	docs/architecture.md
flok-0.0.91	docs/architecture.md
flok-0.0.90	docs/architecture.md
flok-0.0.89	docs/architecture.md
flok-0.0.88	docs/architecture.md
flok-0.0.87	docs/architecture.md
flok-0.0.86	docs/architecture.md
flok-0.0.85	docs/architecture.md