<html><body>
<p>Someone also suggested that object naming move to join caching. If we take Jesper's suggestion then object naming would become part of this new chapter too. <br>
<br>
It all makes sense to me but I do not know who has the cycles to do the work. I do not<br>
<br>
Dick <br>
<br>
Dick Treumann - MPI Team/TCEM <br>
IBM Systems & Technology Group<br>
Dept 0lva / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601<br>
Tele (845) 433-7846 Fax (845) 433-8363<br>
<br>
<br>
<tt>mpi-21-bounces@lists.mpi-forum.org wrote on 04/09/2008 02:50:22 AM:<br>
<br>
> <br>
> Dick, Rolf, all,<br>
> <br>
> On Tue, Apr 08, 2008 at 07:46:27PM -0400, Richard Treumann wrote:<br>
> > <br>
> > 4) The discussion of attribute caching needs significant rework. It has<br>
> > paragraphs from when only communicators supported caching and paragraphs<br>
> > about adding caching support to windows and datatypes. It should be<br>
> > reworded to describe caching as it applies to all three object types and<br>
> > explain who there is no WIN_DUP while there is a TYPE_DUP and a COMM_DUP.<br>
> > (and therefore no attribute copy functions for windows.)<br>
> > <br>
> I agree with that. A not so modest proposal (requiring work) would be<br>
> to have a seperate chapter on object caching, and merge that with the <br>
> chapter on the info object (which is too short on its own, and still has <br>
> the hopeless "miscellany" title)?<br>
> <br>
> Jesper<br>
> <br>
> [attachment "smime.p7s" deleted by Richard <br>
> Treumann/Poughkeepsie/IBM] _______________________________________________<br>
> mpi-21 mailing list<br>
> mpi-21@lists.mpi-forum.org<br>
> <a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-21</a><br>
</tt></body></html>