Hi Jean, Please see my response inline.
On 02/23/10 02:58 PM, jeanm wrote: > Karen, > > Thanks for the additional input. > > On 02/23/10 01:45 PM, Karen Tung wrote: >> Hi Jean, >> >> A few more things I forgot while I was reviewing the doc yesterday. >> >> In the existing transfer module, there's special logic there to deal >> with the symlinks that are created from /etc and /var for the >> solarismisc.zlib. >> How will those be handled with the new design? > > > Since that logic, a.k.a. the do_clobber function, really didn't belong > in the transfer > module it won't be included. It should however be dealt with > somewhere, you're right. > I'll ask Sarah for direction on where. Sounds good. I just want to make sure that functionality is accounted for "somewhere". > >> >> Since this is to improve on the current transfer module, it would be >> good >> to have a section in the doc that talks about what problem the >> current transfer module have, and how the new design will solve those >> problems. > > I'll add this to the Purpose statement since it does seem to belong > there. > The updated Purpose statement in version 2.0 of your doc looks good to me. >> Also, it would be good to have a mapping on how all the existing >> functionalities are mapped to the functionalities in the new design. >> > Section 5 Functionality mapping ????? > > With a table that would give old v.s. new? That would be helpful, I think. It will be useful for everybody to see that all currently useful functionalities in the transfer module are accounted for. Thanks, --Karen
