<HTML>
<HEAD>
<TITLE>Re: [Mpi3-ft] Weekly con-calls</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Just a reminder about tomorrow’s call.<BR>
Rich<BR>
<BR>
<BR>
On 9/16/08 5:05 PM, "Richard Graham" <<a href="rlgraham@ornl.gov">rlgraham@ornl.gov</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Lets resume these meetings on Wed next week, 9/24/2008, noon-2pm Eastern time – moving this an hours later does not work for the people from Japan. What we want to talk about next time are specific user use-cases. We have talked so far in generalities, but now need to get to specifics in term of how apps actually want to use this functionality. As an example, take the case of client/server apps, with a failure in on of the “clients”. If the client is member of the remote group in the intercommunicator, fully defining error scenarios in the current MPI-2 dynamics should be sufficient. However, if a member of the failed client is in the some comm_world as the sever then we need to define new semantics. These are the sort of details we need to get to, so please bring as much input as you can from the user communities you work with.<BR>
<BR>
Call details:<BR>
Wed - 12-2 pm EDT, 5-7 pm GMT<BR>
US Toll Free number: 877-801-8130<BR>
Toll number: 1-203-692-8690<BR>
Access Code: 1044056<BR>
<BR>
Rich<BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></SPAN></FONT><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
mpi3-ft mailing list<BR>
<a href="mpi3-ft@lists.mpi-forum.org">mpi3-ft@lists.mpi-forum.org</a><BR>
<a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-ft</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>