I think that we should follow stick as closly as possible to the sockets model on this one. However, whatever way we go, I agree with Arkady that we should...
I completely agree. I think many in the collaborative have long held the belief that we should follow existing practice and principle wherever possible to...
Topper, Anthony
Anthony.Topper@...
Jun 3, 2002 4:11 pm
1182
DAT collaborative members, If you are planning to attend the face-to-face either in person or via the bridge and have not already let me know, please do so as...
Folks: I propose that the uDAPL and kDAPL specifications be ratified as it exists today this Wednesday. Rationale: * We have been in operation for close to a...
Should we include the IA_address for the IA attributes in the same format as in all other places (DAT_IA_ADDRESS_PTR) for ratification? We will later fix that...
The current list of attendees that I have to date are: In person: Arkady Kanevsky (NetApp) Anthony Topper (NetApp) Ken Walker (Lane15) Heidi Scott (IBM DB2) ...
Hello, I second the motion. Same reasoning - we better get closed to start getting implemntations in core going so Rwe can look into real applications doing ...
bbialek@...
Jun 3, 2002 4:49 pm
1189
Both kDAPL and uDAPL specs has been posted for ratification last week in the file area of the reflector. Any ammendments to the specs will be compiled into a...
I have just uploaded dat_registry 0.8 to yahoogroups. http://groups.yahoo.com/group/dat-discussions/file/dat_registry_08.pdf It is the first draft of the DAT...
Below are some of the minor fixes in kDAPL-0.999 and uDAPL-0.95 specs posted for ratification. 1. uDAPL page 103, line 23: ep_atributes -> ep_attributes 2....
If you are not on the list below and you intend to attend the June 13-14 face-to-face either in person or via the bridge, please let me know no later than this...
... I agree. The "open issues" are very minor points regarding the representation of addresses. It's easy to focus on the remaining issues and overlook what...
I went through my various notes and compiled the following list of ideas that have been kicked around, but postponed until after 1.0. getsockname/getpeername...
RD must be on this list. Provite data on reject should also be there. And lets not forget connection request redirection (not just hand-off). I propose that...
Reminder, that we will vote on the uDAPL and kDAPL specs today. Hope you can make it for the vote! Arkady Chair of DAT Collaborative Arkady Kanevsky email:...
Caitlin, we talked about dat_ia_open api as two part api. One is provider api & another is part of registration library which loads the library and opens the...
I came across an interesting name resolution api that may be of interest. The getaddrinfo(.) and getnameinfo(.) functions, supported in Solaris 8 and Linux,...
... Sri and I discussed those during one of the conference calls. Well, technically *everyone* discussed it, but I kind of had the feeling that we were the...
The System Fabric Works, Inc., the successor to the IB Source, has formally joined DAT Collaborative. It replaces IB Source membership. Welcome back Bob. ...
Enclosed, please, find the Provider Registration. This is the kDAPL spec chapter 7. The uDAPL is analogous with only the headers at the end different. Please,...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
