Fork us on GitHub Follow us on Google+ Follow us on Facebook Follow us on Twitter

Changes between Initial Version and Version 1 of Ticket #424


Ignore:
Timestamp:
2012-03-08T13:47:59Z (6 years ago)
Author:
Jiri Svoboda
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #424 – Description

    initial v1  
    1 In the majority of cases we converged to using IPC as a means of doing remote procedure calls. We 'trivially' wrap IPC communication into a C API. There is a lot of repetitive effort associated with writing such code, which could be automated.
     1In the majority of cases we have converged to using IPC as a means of performing remote procedure calls. We 'trivially' wrap IPC communication into a C API. There is a lot of repetitive effort associated with writing such code, which could be automated.
    22
    33We should introduce a simple interface definition language and generate the IPC code from that. An interface definition might consist of:
     
    1212  * list of input and output arguments (and their types)
    1313
    14 The allowed types depend on the level of sophistication of the implementation and can range from simle (integer) to more complex (string, struct, array).
     14The allowed types depend on the level of sophistication of the implementation and can range from simple (integer) to more complex (string, struct, array).
    1515
    16 By compiling the an interface definition we would obtain a set of C+header files containing:
     16By compiling an interface definition we would obtain a set of C+header files containing:
    1717  * enums declaring method and event codes
    1818  * typedefs encapsulating the interface instance for server and client