Subject: Re: [Simple] draft-ietf-simple-partial-publish-03 - in what cases exactly the compositor send 500?

From: Aki Niemi <[email-masked]>
Date: Thu, 20 Oct 2005 16:51:34 +0300

Sorry for the late response. Inline.

ext Anat Angel wrote:
> Hi
> 
>  
> 
> This draft states in par 4.3.1 that:
> 
> "If any errors are encountered before the entire publication is
> 
>    completely processed, the compositor MUST reject the request with a
> 
>    500 (Server Internal Error) response, and revert back to its
> 
>    original, locally stored presence information."
> 
>  
> 
> My question is:
> 
> Does this mean that if xml parsing fails (for example), 500 must be sent?
> 
> If so, why is it different from the behavior in rfc 3903 for pidf?

It really isn't different. The last part of step 5 in Chapter 6 of RFC 
3903 talks about this very issue.

However, I agree that what exactly constitutes such an "internal" server 
error is left quite open, in both PUBLISH as well as partial-publish. 
This is simply because at the time of writing RFC 3903 -- and even today 
to some extent -- it isn't well understood what a presence composer 
function does with the inputs it receives. Particularly, whether it 
checks for validity or well-formedness, and whether it rejects 
publications that are not valid or well-formed XML, or is simply liberal 
in what it receives and recovers somewoh, is still somewhat under 
discussion.

Simply put, it depends. ;)

There is work ongoing, though, and you should probably check this draft:
http://www.ietf.org/internet-drafts/draft-schulzrinne-simple-composition-00.txt

Cheers,
Aki

>  
> 
> Thanks,
> 
> Anat Angel
> 
>  
> 
>  
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Simple mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/simple

_______________________________________________
Simple mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/simple