Meetings 2011-08-02¶

Filtering on Types¶

Problem description:

Scope for Camera settings:

/vision/cam/setting

Problem:
Subscription on /vision

User handler gets payloads of different types.

Decisions¶

• Provide templated filtering data handler which allows filtering for specific types per handler
  • accepts only the specified data types

Request/Reply Subsystem¶

Client API¶

• Expose two callback interfaces?
  1. "boxed": Event -> Event?
  2. "unboxed": RequestType -> ReplyType?
• Callback registration in Java?
• How do we deal with signatures of remote methods?
  • Are signatures of remote methods known at call-time?
  • C++: call<string, string>("echo", "bla") seems ok
  • Java:
    • call<String, String>("echo", "bla") not possible, right?
    • ((RemoteMethod<String, String>) getMethod("echo")).call("bla")?
  • Python: type(arg)?
  • Lisp: type-of(arg), check-type?

Introspection¶

• Should the client be able to query the server for its set of supported methods?
• If so, should request and reply types be included?

Protocol¶

• Do we need the ability to wait a server to become ready (or rather, for a service to be provided by at least one remote server)?
  • Would be convenient for writing the integration test
  • Disadvantage: added complexity, source of errors
• Do we need method calls without replies?
• #458
  • Disadvantages: less info for logger, Jens