Skip to content

Update cosmo.properties - #1

Merged
wsdwl merged 1 commit into
mam-dev:masterfrom
eisler:patch-1
Jun 18, 2015
Merged

wsdwl merged 1 commit into
mam-dev:masterfrom
eisler:patch-1

Conversation

@eisler

@eisler eisler commented Jun 18, 2015

Copy link
Copy Markdown
Contributor

please use example.com for domain names in configuration files.

wsdwl added a commit that referenced this pull request Jun 18, 2015
Update cosmo.properties - has been overlocked. Thanks!
@wsdwl
wsdwl merged commit e552b4c into mam-dev:master Jun 18, 2015
f1-outsourcing pushed a commit to f1-outsourcing/cosmo that referenced this pull request Aug 29, 2026
fix: emit RFC 6578 change-log entries (D+C) on cross-collection MOVE

StandardContentService#moveItem now writes a DAV:sync-collection
tombstone (D-row) at the source collection and a live member (C-row)
at the destination, per RFC 6578 §3.2/§5 (a rename/move is reported
as delete at the old href + create at the new href).

- D-row logged before removeItemFromCollection (source tombstone)
- C-row logged after addItemToCollection (destination live member)
- Guarded by crossCollection so same-parent renames (single M-row via
  updateContent) do not double-log
- Applied in both the locking ContentItem branch and the plain branch

Test (I2):
- Rewrote crossCollectionMoveEmitsTombstoneInSourceAndLiveMemberInTarget
  to lock the RFC-compliant shape: exactly one bare-404 tombstone in
  A's incremental sync, exactly one live 200 getetag entry in B's
- Fixed three test-bug helpers:
  * OutputKeys is a top-level class (not Transformer.OutputKeys)
  * hrefStartsWithPrefix now decodes the percent-encoded collectionUri
  * B-side 200 lives INSIDE the propstat (Cosmo/RFC 4918 shape), not
    as a response-level DAV:status

Docs: rfc-compliance.md (Known Limitations mam-dev#1, Roadmap mam-dev#5) and
synccollection-testcases.md (I2 rows, notes, status, traceability)
updated to reflect the implemented behavior.

Full cosmo-core suite: 395/395 green.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants