[ From jgh ] Meeting: Thursday 5th December 2002 21:00GMT (16:00EST, 13:00PST) Toll Free (US & Canada): 1-888-742-8686 International: +1-303-928-2600 Conference ID: 3378790 Attendees: Jeremy Harris, Sun Juliana Hsu, IBM Vish Subramanian, HP John Kasperski, IBM Louis Laborde, HP Apologies: Dave Edmondson, Sun ------ Agenda: 1. Questions raised on the list 1.1 (Jeff Messing) Memory Deregister call flags - what about out-of-range values? Do we want a default operation, with modifier flags? a) Implementations should error-check the arguments. b) No concensus for which op should be default. Leave as per API v0.5 specification. 1.2 (Vish) exs_qstatus: Should this be analogous to exs_qmodify? [I didn't record the points raised un discussion, sorry] Concensus was yes, probably. AI: Vish to publish new function prototype & semantic on the list, for later approval. 1.3 (Jeff) Wasn't the async verison of sendfile/recvfile to be folded back into send/recvmsg? Concensus: No, not enough support. 1.4 (Jeff) exs_qhandle_t is typdef'd as an int. Why isn't this a void * similar to the exs_mhandle_t? Concensus: Accept; a void * permits implementations where the queue handle is a pointer while still supporting those where it is a file-descriptor (integer). The current does not. AI: Louis to up-rev the API. 1.5 (Louis) shouldn't qdelete only fail if there are still async ops in flight and not if there are still event registered? Why force the user to deregister all events if that can be done in qdelete? No concensus. Issues: - May cost implementation to track inflight async ops, rather than registrations - Some hardware may make it difficult to cancel/retrieve inflight ops. AI: (Everybody!) continue discussion on the list. Recommendation: Implementations should document their behaviour on async-op cancels; whether a cancel always succeeds, may fail (in what situations), always fails. At this point we ran out of time. There are still outstanding queries from Louis, at the top of his API v0.5 posting. Discussion to continue on the list and at the next concall. Future Topics: -------------------------------- Outstanding Actions: 2002-04-18/02 dme. Draft a paper describing why a unified socket/file IO API would be useful. Kick David. 2002-08-06/01 dme. Produce a clarification on the results of the C3.1 and C7 vote. Pending clarification of the event queue <-> socket binding scope. 2002-10-01/02 dme. Update the requirements specification to conform with recent agreements. 2002-10-03/01 dme. Shared memory flag: add to the requirements specification and draft API. 2002-10-03/02 dme. Sendfile/recvfile: draft an update to the requirements specification to include the opinion at the meeting. 2002-12-05 vish. Publish prototype for proposed exs_qstatus() prototype and semantics, on the mailinglist. 2002-12-05 louis. New API revision. -------------------------------- Next Meeting: Thursday 12th December 2002 21:00GMT Toll Free (US & Canada): 1-888-742-8686 International: +1-303-928-2600 Conference ID: 3378790 Alternate teleconference numbers: Toll Free (US & Canada): 1 877 214 5010 International: +1 (504) 588 9772 Code: 769497 -------------------------------- Contact Details: email: icsc-socketwg@opengroup.org web: http://www.opengroup.org/icsc/sockets/protected