Credentials from IIS to Exchange

I believe in Example 1, the binding of C5 named E
should be to a new resource (e.g., C6), and C6 has a binding named B to
C4.
In Example 2, the two new members of C4 should be
new resources (e.g., C5 and C6), not C2 and C3 (that might have just been
a typo).  And the binding of C6 named E should be a new resource (e.g.,
C7), and C7 has a binding named B to C5.
So in each example, a copy never creates a binding
back to an existing resource, so 3 new resources would be created by the
copy.
Cheers,
Geoff
Tim wrote on 08/25/2006 12:27:52 PM:

> Hello,

> 

> I just wanted to verify some examples my team and I have some up 

> with with regard to COPY in the place of BIND loops.

> 

> 

> Example 1:

> 

>    +--------+

>    |        |

>    |  Root  |

>    |        |   

>    | A      |   

>    +--------+   

>      |          

>      |

>      |

>    +--------+

>    |        |

> +--|  C1    |

> |  |        |   

> |  | B      |   

> |  +--------+   

> |    |          

> |    |         

> |    |          

> |  +--------+   

> |  |        |  

> |  |  C2    |   

> |  |        |  

> |  | D      |   

> |  +--------+   

> |    |          

> |    |          

> |    |          

> |  +--------+   

> |  |        |   

> |  |  C3    |   

> |  |        |   

> |  | E      |   

> |  +--------+   

> |    |          

> |    |          

> +----+ 

> 

> COPY /A/B  to  /A/F  results in:

> 

>    +--------+

>    |        |

>    |  Root  |

>    |        |   

>    | A      |   

>    +--------+   

>      |          

>      |

>      |

>    +--------+

>    |        |

> +--|  C1    |---------------+

> |  |        |        
      |

> |  | B    F |            
  |

> |  +--------+              
| 

> |    |    |          
      |

> |    |    +-------+        
|

> |    |            |  
      |

> |  +--------+   +--------+  | 

> |  |        |   |      
 |  | 

> |  |  C2    |   |  C4    |
 | 

> |  |        |   |      
 |  | 

> |  | D      |   | D      |
 | 

> |  +--------+   +--------+  | 

> |    |            |  
      | 

> |    |            |  
      | 

> |    |            |  
      | 

> |  +--------+   +--------+  | 

> |  |        |   |      
 |  | 

> |  |  C3    |   |  C5    |
 | 

> |  |        |   |      
 |  | 

> |  | E      |   | E      |
 | 

> |  +--------+   +--------+  | 

> |    |            |  
      | 

> |    |            |  
      |

> +----+            +---------+ 

> 

> 

> 

> Example 2:

> 

> 

>    +--------+

>    |        |

>    |  Root  |

>    |        |   

>    | A    F |   

>    +--------+   

>      |    |      

>      |    +--------+

>      |             |

>    +--------+  +--------+ 

>    |        |  |    
   | 

> +--|  C1    |  |  C4    | 

> |  |        |  |      
 |   

> |  | B      |  |        |

> |  +--------+  +--------+   

> |    |              

> |    |         

> |    |          

> |  +--------+   

> |  |        |  

> |  |  C2    |   

> |  |        |  

> |  | D      |   

> |  +--------+   

> |    |          

> |    |          

> |    |          

> |  +--------+   

> |  |        |   

> |  |  C3    |   

> |  |        |   

> |  | E      |   

> |  +--------+   

> |    |          

> |    |          

> +----+

> 

> 

> COPY /A/B to /F/G results in: 

> 

> 

>    +--------+

>    |        |

>    |  Root  |

>    |        |   

>    | A    F |   

>    +--------+   

>      |    |      

>      |    +--------+

>      |             |

>    +--------+  +--------+ 

>    |        |  |    
   | 

> +--|  C1    |  |  C4    |--+

> |  |        |  |      
 |  | 

> |  | B      |  | G      |
 | 

> |  +--------+  +--------+  | 

> |    |           |    
    |         

> |    |           |    
    |

> |    |           |    
    | 

> |  +--------+  +--------+  | 

> |  |        |  |      
 |  |

> |  |  C2    |  |  C2    |
 | 

> |  |        |  |      
 |  |

> |  | D      |  | D      |
 | 

> |  +--------+  +--------+  | 

> |    |           |    
    | 

> |    |           |    
    | 

> |    |           |    
    | 

> |  +--------+  +--------+  | 

> |  |        |  |      
 |  | 

> |  |  C3    |  |  C3    |
 | 

> |  |        |  |      
 |  | 

> |  | E      |  | E      |
 | 

> |  +--------+  +--------+  | 

> |    |           |    
    | 

> |    |           |    
    | 

> +----+           +---------+

> 

> 

> 

> Are both these examples correct? 

> 

> thanks,

> Tim

> 

I believe in Example 1, the binding of C5 named E
should be to a new resource (e.g., C6), and C6 has a binding named B to
C4.
In Example 2, the two new members of C4 should be
new resources (e.g., C5 and C6), not C2 and C3 (that might have just been
a typo).  And the binding of C6 named E should be a new resource (e.g.,
C7), and C7 has a binding named B to C5.
So in each example, a copy never creates a binding
back to an existing resource, so 3 new resources would be created by the
copy.

I believe in Example 1, the binding of C5 named E should be to a new resource
(e.g., C6), and C6 has a binding named B to C4.

In Example 2, the two new members of C4 should be new resources (e.g.,
C5 and C6), not C2 and C3 (that might have just been a typo).  And
the binding of C6 named E should be a new resource (e.g., C7), and C7 has
a binding named B to C5.

So in each example, a copy never creates a binding back to an existing
resource, so 3 new resources would be created by the copy.
Hi Julian,

Julian Reschke wrote:

Hi,

as a follow up to BugZilla issue 247
(http://ietf.osafoundation.org:8080/=
bugzilla/show_bug.cgi?id=3D247>) which
I opened a few days ago (but which was originally raised during Last
Call) I'm currently confused by statements like:

   COPY/MOVE behaviour:  This property value SHOULD be kept during a
      MOVE operation, but is normally re-initialized when a resource is
      created with a COPY.  It should not be set in a COPY.

(see
<http://gree=
nbytes.de/tech/webdav/draft-ietf-webdav-rfc2518bis-15.html#rfc.section.15=
.1>).

Questions:

1) When a resource is being created, shouldn't DAV:creationdate *always*
be set (by definition?)

My understanding of this is that the property is indeed set when a new
resource is created during a COPY.

2) What does "should not be set in a COPY" mean? What =
does "in a COPY"
refer to?

I think this refers to the case when an existing resource is overwritten.
The creationdate shouldn't be updated because the resource is merely
being updated. The getlastmodified property on the other hand would be
set, but to the value corresponding to the time of the COPY operation.

There are similar problems with other COPY/MOVE behavi=
our statements,
but maybe we can focus on this one first...

Best regards, Julian

Best regards,

Werner.