3. Client Definitions

[juanpedromoreno]

Related to #9

1. Clients should be generated outside of the protocol and server definitions module and based on the .protofiles generated by the Protocol definition in 1. Define Protocol Format Definitions #9
2. A client has a direct correlation to a @service definition and its sole concern is communicating with the remote @service. A client may be generated as shown below:

@client[Greeter] trait GreeterClient

Combinators instrospected from the protocol definitions and made synthetic in the client trait via macro should expose operation as @free algebras with default implementations provided as implicit instances in the client's companion. These handlers as everything in Freestyle should be overridable and able to target any M[_] : AsyncContext capable monads. (Streaming capabilities TBD).
3. Clients should remain scala.js compatible (it'll be addressed in #21)
4. Clients synthetic handlers should impose implicit evidence of the remote endpoint configuration for the service.

• Client Derivation based on protocol definitions (it'll be addressed in Protocol Definitions - Client Macro Definitions #28 )
• Clients correlated with Service definitions for unary Services (fixed in Client Definitions based on free algebras - Unary Services  #16)
• Clients correlated with Service definitions for client streaming services
• Clients correlated with Service definitions for server streaming services
• Clients correlated with Service definitions for bidirectional streaming services

[juanpedromoreno]

The three remain items will be tackled as a part of #30