If you go with the Remote<'T>.xxx syntax for remoting (as opposed to calling Rpc/Remote-annotated functions seamlessly), 'T has traditionally been a class with instance members representing the remote procedures. Other tickets in the pipeline, most notably #1047 aims to extend this with interfaces, and #1336 changes RPC communication to be transparent and open to other clients.
This ticket adds the ability to use F#/C# records to specify remote capabilities. Roughly speaking, it enables connecting WebSharper clients to Fable.Remoting servers with the same contract notation.
If you go with the
Remote<'T>.xxxsyntax for remoting (as opposed to callingRpc/Remote-annotated functions seamlessly),'Thas traditionally been a class with instance members representing the remote procedures. Other tickets in the pipeline, most notably #1047 aims to extend this with interfaces, and #1336 changes RPC communication to be transparent and open to other clients.This ticket adds the ability to use F#/C# records to specify remote capabilities. Roughly speaking, it enables connecting WebSharper clients to Fable.Remoting servers with the same contract notation.