[Standards] Updated: Event logging over XMPP

Steffen Larsen zooldk at gmail.com
Wed Nov 13 19:00:33 UTC 2013


No problem Peter, You did all the hard job.. I am just commenting. :-)

/Steffen

On 13 Nov 2013, at 19:09, Peter Waher <Peter.Waher at clayster.com> wrote:

> Hello Steffen
> 
> Ok, I see. It might be, as you say, implementation specific. Our implementation accepts any number of child elements. But that might not be the case for everybody perhaps. I have no idea.
> 
> Anyway, I've added a section §3.9 (new version attached) to show how multiple events can be sent in a single message to clarify that the receiving end needs to support this. Good thinking to point this out. Thanks.
> 
> Best regards,
> Peter Waher
> 
> 
> -----Original Message-----
> From: Steffen Larsen [mailto:zooldk at gmail.com] 
> Sent: den 13 november 2013 12:47
> To: XMPP Standards
> Subject: Re: [Standards] Updated: Event logging over XMPP
> 
> Hi Peter,
> 
> I was thinking the same, that you could put multiple log elements into the message.. But then client or component should in the other end always try to "read" multiple <log> structures out of the message stanza.
> It should be possible, but on the other side how do we treat the other tags inside the stanzas?  I mean most client parsers probably only expect one <body> element.. I don't know if that multiple elements should be stated explicitly.
> 
> -Cheers!
> 
> /Steffen
> 
> On 13 Nov 2013, at 14:58, Peter Waher <Peter.Waher at clayster.com> wrote:
> 
>> Hello Steffen
>> 
>> Thanks for the feedback. It's a good point that you might want to send multiple events in the same message. But would that not be accomplished with the current structure, but with multiple <log> elements? As so:
>> 
>>  <message from='device at clayster.com/device' to='eventlog at clayster.com' type='normal' xml:lang='en'>
>>     <log  xmlns='urn:xmpp:eventlog' timestamp='2013-11-10T15:52:23Z'>
>>        <message>Something happened.</message>
>>     </log>
>>     <log  xmlns='urn:xmpp:eventlog' timestamp='2013-11-10T15:54:23Z''>
>>        <message>Something else happened.</message>
>>     </log>
>>  </message>
>> 
>> Or do client implementations suppose only one custom element is sent per message?
>> 
>> If the above would work, should I add an Implementation Note regarding this? 
>> 
>> Best regards,
>> Peter Waher
>> 
>> -----Original Message-----
>> From: Steffen Larsen [mailto:zooldk at gmail.com] 
>> Sent: den 13 november 2013 06:05
>> To: XMPP Standards
>> Subject: Re: [Standards] Updated: Event logging over XMPP
>> 
>> Hi,
>> 
>> I really think we have made some progress on this one. So cool Peter! :-)
>> Just want to add a small thing: I have some logging like this already on my clients, and when the information is not that important I sometime piggy back the event log into one message stanza.
>> So what I really would like to do is, to be able to have multiple <log> tags.
>> 
>> So maybe like this:
>> 
>>  <message from='device at clayster.com/device' to='eventlog at clayster.com' type='normal' xml:lang='en'>
>>     <log> 
>> 	<event xmlns='urn:xmpp:eventlog'
>>          message='Something happened.'
>>          timestamp='2013-11-10T15:52:23Z' />
>> 	<event xmlns='urn:xmpp:eventlog'
>>          message='Something else happened.'
>>          timestamp='2013-11-10T15:54:23Z' />
>>   </log>
>>  </message>
>> 
>> Is it totally crazy?
>> Coming back to the naming.. Now here is a log, consisting of multiple events..  
>> Of course I would only do this If the logged events are not that important and needed to be near real-time. :-)
>> 
>> -Just my 50 cent
>> /Steffen
>> 
>> 
>> On 12 Nov 2013, at 16:30, Peter Waher <Peter.Waher at clayster.com> wrote:
>> 
>>> Hello
>>> 
>>> I've updated the event logging proposal following the discussion with Dave. I've made the message and stackTrace attributes into child elements instead, better suited for multi-line text. I've also added some more security considerations and reference to the publish/subscribe pattern.
>>> 
>>> I've attached the latest versions.
>>> 
>>> Best regards.
>>> Peter Waher
>>> 
>>> 
>>> 
>>> <eventlogging.html><eventlogging.xml><eventlogging.xsd>
>> 
> 
> <eventlogging.html><eventlogging.xml>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4130 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20131113/8fe2e9ec/attachment.bin>


More information about the Standards mailing list