Interconnect Software Consorium Socket API Extensions Working Group. -------------------------------------------------------------------- Meeting: Thursday 3rd October 2002 20:00GMT (21:00BST, 04:00p EDT, 03:00p CDT, 01:00p PDT, 22:00CEST, 05:00JST+) 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 -------------------------------- Attendees: David Edmondson, Sun John Kasperski, IBM Jeff Messing, IBM Satya Sharma, IBM Jeremy Harris, Sun Vish Sumbramanian, HP Louis Laborde, HP Apologies: Masanori Itoh, Fujitsu Juliana Hsu, IBM -------------------------------- Agenda: 1. Agenda bashing. Shared memory flag (see Vish). Sendfile. One shot registrations. API 0.3. 2. Review action items. See below. 3. Approve Last Minutes. dme forgot to ask. 4. Shared memory flag. No-one objected to the flag. Implementations are free to ignore the flag. Applications are not required to set the flag. Hence, we add the flag. ACTION: dme to add to the requirements specification and draft API. 5. sendfile/recvfile. Various items were discussed (most refer to sendfile - apply the appropriate transformation for recvfile): * Are _any_ files necessary in the vector of inputs/outputs ? If not, why is this called sendfile ? * What destinations are permitted ? General agreement that only file descriptors should be used as destinations. Debate about whether they should be restricted to socket file descriptors. - Indication of an event queue for completion is required. A socket would indicate an event queue. * For source fd's, what types of fd are allowed ? - At least regular files must be supported. - Disagreement about whether this should be a hard limit or a minimum. * The vector needs to updated to indicate what happened in respect of each element at the end of the call. * For recvfile, the final element in the output vector can be a file descriptor with no size indicated. This means "read the source until EOF, writing all of the data to the fd". ACTION: dme to draft an update to the requirements specification to include the opinion at the meeting. The proposal will be discussed by email, with a decision made at the Tuesday meeting. 6. One shot registrations. Postponed to phase 2 by general agreement. 7. API 0.3. Questions from Louis' recent 0.3 API: * - should we keep only the common stuff outside the union in exs_event_t ? * In which case, only evt_type should remain since, for example, evt_status is * not applicable to poll events. Jeremy, Jeff: should remain common. Vish: not strong opinion. {type, status} outside. A discussion about the use of a union followed. There was no clear consensus, so we should discuss on the mailing list. Ran out of time. 8. AOB * Enabling inbound connection notification. - Need to make the association and call listen(). - Ordering between the above two doesn't matter. - At the time the association is made any existing inbound connections which have not been accept()ed should cause notifications to occur. * Need exs_connect() to initiate asynchronous outbound connections. A handle is necessary for cancellation. * Asynchronous events will complete on the event queue which was associated with the socket at the time of the event initiation. If the event queue association of a socket is changed, any outstanding asynchronous operations will therefore complete on the original queue, with newly initiated operations completing on the new queue. * What does the sendfile multi-fd support actually mean ? Multi-fd to multi-fd support has been removed. In the case of recvfile(), data from the source is scattered across the destination vector elements in a manner similar to the way in which data is gathered from the source elements with sendfile(). Future Topics: * Continue API 0.3 review. * sendfile/recvfile file descriptors discussion. -------------------------------- 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-09-26/02 Louis. Draft an update to the API to separate the sendfile and recvfile cases. Done. 2002-10-01/01 dme. Produce a list of 'todo' items for the requirements specification. 2002-10-01/02 dme. Update the requirements specification to conform with recent agreements. 2002-10-01/03 Louis. Update the draft API in line with recent discussions. Done. 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. -------------------------------- Next Meeting: Tuesday 8th October 2002 20:00GMT (21:00BST, 04:00p EDT, 03:00p CDT, 01:00p PDT, 22:00CEST, 05:00JST+) 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 Content-Disposition: form-data; name="link1"