On 02/23/10 03: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 s
Sarah,
Thanks for the phone discussion. As we discussed, most of these issues
were related to the fact that I misunderstood the scope of what I was
responsible for. I was not considering the transfer module checkpoint in
my design. So with
that in mind, comments are inline.
Jean
On 03/ 1/10 0
Hi Jean,
My responses are inline.
- Keith
On 03/ 1/10 02:27 PM, jeanm wrote:
> Keith,
>
> Thanks for the feedback. Comments are inline.
>
> On 02/26/10 04:51 PM, Keith Mitchell wrote:
>> Hi Jean,
>>
>> I reviewed version 2.0 of the document.
>>
>> My first general comment - since there are certa
On 03/ 1/10 05:37 PM, Shawn Walker wrote:
> On 03/ 1/10 04:29 PM, Joseph J. VLcek wrote:
>> My understanding of the design is the Transfer Module will actually
>> present multiple APIs. One for each specific media type. I was wondering
>> if this was really necessary. Wouldn't it be better to have
On 03/ 1/10 05:01 PM, jeanm wrote:
> Joe,
>
> Thanks for the feedback. Response is inline.
>
> Jean
>
> On 02/26/10 10:35 AM, Joseph J VLcek wrote:
>> On 02/22/10 04:32 PM, jeanm wrote:
>>>
>>> Please review the design document for the transfer module of the Caiman
>>> Unified Design project.
>>> I
Hi Jean,
> On 02/25/10 05:27 PM, Sarah Jelinek wrote:
>> Hi Jean,
>>
>> I reviewed v2.0 of the doc. I tried not to repeat others comments.
>>
>>
>> Section 2:
>>> The checkpointing module will be available.
>>
>> I am not sure what this means exactly. The Transfer Module is a
>> 'checkpoint' it w
On 03/ 1/10 04:29 PM, Joseph J. VLcek wrote:
> My understanding of the design is the Transfer Module will actually
> present multiple APIs. One for each specific media type. I was wondering
> if this was really necessary. Wouldn't it be better to have the high
> level API which, implemented as the
On 03/ 1/10 03:00 PM, jeanm wrote:
> Dave,
>
> Thanks for the feedback, questions/comments are inline.
>
>
> On 02/25/10 04:35 PM, Dave Miner wrote:
>> On 02/22/10 04:32 PM, jeanm wrote:
>>>
>>> Please review the design document for the transfer module of the Caiman
>>> Unified Design project.
>>
>
Keith,
Thanks for the feedback. Comments are inline.
On 02/26/10 04:51 PM, Keith Mitchell wrote:
> Hi Jean,
>
> I reviewed version 2.0 of the document.
>
> My first general comment - since there are certain functions that are
> common across all transfer types, I think there may be value in
> d
Joe,
Thanks for the feedback. Response is inline.
Jean
On 02/26/10 10:35 AM, Joseph J VLcek wrote:
> On 02/22/10 04:32 PM, jeanm wrote:
>>
>> Please review the design document for the transfer module of the Caiman
>> Unified Design project.
>> It can be accessed via:
>> http://hub.opensolaris.or
On 02/25/10 05:27 PM, Sarah Jelinek wrote:
> Hi Jean,
>
> I reviewed v2.0 of the doc. I tried not to repeat others comments.
>
>
> Section 2:
>> The checkpointing module will be available.
>
> I am not sure what this means exactly. The Transfer Module is a
> 'checkpoint' it will implement checkpoi
On 03/ 1/10 02:00 PM, jeanm wrote:
> Dave,
>
> Thanks for the feedback, questions/comments are inline.
>
>
> On 02/25/10 04:35 PM, Dave Miner wrote:
>> On 02/22/10 04:32 PM, jeanm wrote:
>>>
>>> Please review the design document for the transfer module of the Caiman
>>> Unified Design project.
>>
>
Dave,
Thanks for the feedback, questions/comments are inline.
On 02/25/10 04:35 PM, Dave Miner wrote:
> On 02/22/10 04:32 PM, jeanm wrote:
>>
>> Please review the design document for the transfer module of the Caiman
>> Unified Design project.
>
> Reviewed version 2.0.
>
> I have a general quest
On 02/25/10 05:32 PM, Shawn Walker wrote:
> On 02/24/10 05:53 PM, jeanm wrote:
>> It's been called to my attention that the link I posted was a
>> preview/edit link. Here's the real one:
>> http://hub.opensolaris.org/bin/download/Project+caiman/CUE_docs/CUDTransferModule.odt
>>
>>
>
> I get:
>
>
Hi Jean,
I reviewed version 2.0 of the document.
My first general comment - since there are certain functions that are
common across all transfer types, I think there may be value in defining
a superclass and moving some of the functionality there. Subclasses can
then implement specific attrib
On 02/26/10 03:11 PM, Karen Tung wrote:
...
> On 02/23/10 02:44 PM, jeanm wrote:
...
>> On 02/22/10 05:47 PM, Karen Tung wrote:
...
>>> - There's no discussion about how, if any progress will be reported
>>> back to the caller of
>>> the transfer module. Does the caller pass in a callback function?
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
Hi Jean,
Please see my follow up questions/comments inline.
I removed items that I have no further comments on.
On 02/23/10 02:44 PM, jeanm wrote:
> Karen,
>
> Thanks for your comments. Responses are inline.
>
> Jean
>
> On 02/22/10 05:47 PM, Karen Tung wrote:
>> Hi Jean,
>>
>> Here are my comme
On 02/25/10 05:35 PM, Dave Miner wrote:
> On 02/22/10 04:32 PM, jeanm wrote:
>>
>> Please review the design document for the transfer module of the Caiman
>> Unified Design project.
>
> Reviewed version 2.0.
>
> I have a general question here. Do you feel that implementing an
> IPSTransfer API that
On 02/22/10 04:32 PM, jeanm wrote:
>
> Please review the design document for the transfer module of the Caiman
> Unified Design project.
> It can be accessed via:
> http://hub.opensolaris.org/bin/preview/Project+caiman/CUE_docs/CUDTransferModule.odt
>
>
> I would appreciate feedback by COB Friday F
On 02/26/10 11:45 AM, Joseph J VLcek wrote:
> On 02/22/10 04:32 PM, jeanm wrote:
>>
>> Please review the design document for the transfer module of the Caiman
>> Unified Design project.
>> It can be accessed via:
>> http://hub.opensolaris.org/bin/preview/Project+caiman/CUE_docs/CUDTransferModule.od
On 02/22/10 04:32 PM, jeanm wrote:
>
> Please review the design document for the transfer module of the Caiman
> Unified Design project.
> It can be accessed via:
> http://hub.opensolaris.org/bin/preview/Project+caiman/CUE_docs/CUDTransferModule.odt
>
>
> I would appreciate feedback by COB Friday F
On 02/22/10 04:32 PM, jeanm wrote:
>
> Please review the design document for the transfer module of the Caiman
> Unified Design project.
Reviewed version 2.0.
I have a general question here. Do you feel that implementing an
IPSTransfer API that's this extensive is actually worth the trouble? O
On 02/24/10 05:53 PM, jeanm wrote:
> It's been called to my attention that the link I posted was a
> preview/edit link. Here's the real one:
> http://hub.opensolaris.org/bin/download/Project+caiman/CUE_docs/CUDTransferModule.odt
I get:
"This template does not exist"
...when I try to view it.
--
Hi Jean,
I reviewed v2.0 of the doc. I tried not to repeat others comments.
Section 2:
> The checkpointing module will be available.
I am not sure what this means exactly. The Transfer Module is a
'checkpoint' it will implement checkpoint so if that's what you mean,
sure, but if you expect th
I've updated the document to reflect the feedback from Karen. The link
can be found under:
http://hub.opensolaris.org/bin/view/Project+caiman/CUE_docs
And look for the transfer module design at the bottom.
Jean
On 02/24/10 04:53 PM, jeanm wrote:
> It's been called to my attention that the link
It's been called to my attention that the link I posted was a
preview/edit link. Here's the real one:
http://hub.opensolaris.org/bin/download/Project+caiman/CUE_docs/CUDTransferModule.odt
Sorry,
Jean
On 02/22/10 02:32 PM, jeanm wrote:
>
> Please review the design document for the transfer mo
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 t
Karen,
Thanks for your comments. Responses are inline.
Jean
On 02/22/10 05:47 PM, Karen Tung wrote:
> Hi Jean,
>
> Here are my comments:
>
> General Comments:
> -
>
> - In each of the object types for the 3 different transfer types
> discussed in the
> document,
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 this is to impro
Hi Jean,
Here are my comments:
General Comments:
-
- In each of the object types for the 3 different transfer types
discussed in the
document, there are attributes that will get used by every single
operation within that object type, like the "destination directo
Please review the design document for the transfer module of the Caiman
Unified Design project.
It can be accessed via:
http://hub.opensolaris.org/bin/preview/Project+caiman/CUE_docs/CUDTransferModule.odt
I would appreciate feedback by COB Friday February 26th.
Jean McCormack
32 matches
Mail list logo
