Summary: | Adapt tests according the latest protocol update. | ||
---|---|---|---|
Product: | Ytstenut | Reporter: | Danilo Cesar Lemes de Paula <danilo.eu> |
Component: | tp-ytstenut | Assignee: | Robert Staudinger <robert.staudinger> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | jonny.lamb, olli.salli |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | patch |
Description
Danilo Cesar Lemes de Paula
2012-01-25 02:46:18 UTC
At the same time we should make up our mind whether the capability namespace ends with a : or a # urn:ytstenut:capabilities: vs urn:ytstenut:capabilities# Olli, would now be a good time to move to the # consistently? (In reply to comment #1) > At the same time we should make up our mind whether the capability namespace > ends with a : or a # > > urn:ytstenut:capabilities: vs > urn:ytstenut:capabilities# > > Olli, would now be a good time to move to the # consistently? I think this is a good idea; then, it's clear where the urn ends and the capability starts. However, I have to double-check the places where we transport this as some XMPP protocol construct, to verify the hash sign doesn't have any special meaning in any of them. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.