1 / 8

Some XCON ideas

Some XCON ideas. Henning Schulzrinne Dept. of Computer Science Columbia University hgs@cs.columbia.edu. Assumptions. Avoid transactions and similar constructions difficult to implement  request is atomic Map closely to existing conference data structures

donniegreen
Download Presentation

Some XCON ideas

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Some XCON ideas Henning Schulzrinne Dept. of Computer Science Columbia University hgs@cs.columbia.edu IETF63 - XCON

  2. Assumptions • Avoid transactions and similar constructions • difficult to implement •  request is atomic • Map closely to existing conference data structures • avoids having to maintain two similar, but different structures • use superset of existing structure • Avoid two-level mechanism • Re-use well-known RPC mechanism • Use inheritance (no templates) • closely related concepts – confusing to have both • Affinity to CCCP, but further simplified IETF63 - XCON

  3. Avoid two-level design “dial-out user” adds little abstraction depth get/set/delete something IETF63 - XCON

  4. Re-use RPC • No need to design yet another remote procedure call (RPC) mechanism • Use SOAP – not prettiest, but by far the most popular • clients, servers, tools available in just about any language and OS • don’t know about Fortran and COBOL • well-understood by developer community • no need for protocol-level testing IETF63 - XCON

  5. Example • Does not include standard SOAP header • e.g., addConference <conference-description> <subject>XCON</subject> <service-uris> <entry> <uri>http://example.com/</uri> <purpose>web-page</purpose> </entry> </service-uris> </conference-description> IETF63 - XCON

  6. Operations (~CCCP) • add/change/get/deleteX • Conference • User • Endpoint • Media (for all users) IETF63 - XCON

  7. Open issues • For adding users, can request fail partially • may want to add lots of users at once • add some users, but not others • generally want to proceed even if one user fails • can find out who got added by description returned IETF63 - XCON

  8. What’s missing? • Simple start/end time property for conference • no repeats or the like • Conference media mixing • add floor control property to media • add moderator(s) to user property • define some standard algorithms for now • tiled: ““video follows audio” • no video mixing: “individual” • extend later • define video matrix • (label, width, height) IETF63 - XCON

More Related