On Sun, Dec 19, 2010 at 3:14 PM, Alex North <[email protected]> wrote:
> On 17 December 2010 14:05, Tad Glines <[email protected]> wrote: > >> I think this transition would be easier if there was a defined translation >> to/from the old/new ids. Then WiaB could store/use new ids, but be able to >> support APIs that need to use the old ids. > > > There's two different things going here. One is translating between id > serializations to talk to older APIs. I definitely agree and will implement > that. > > The second is dealing with existing data that uses ids containing > characters that are not valid in the new spec (e.g. '/' inside a token). > Because WIAB has not had persistence, there is no existing data there. It's > easy to define a one-way mapping so that for importing data from Google Wave > or other systems, WIAB can find a new id for broken ones (and update all > references to it on the way). But a two-way mapping is going to be harder. I > don't think it's worthwhile unless someone screams out that making ids > containing '/' invalid (or anything else in the draft spec) is going to > break them. > Why not just URI encode (or similar) the bits that are not allowed in the new spec? Since there is no defined translation from old to new, why not define a translation that ensure that illegal characters in the old spec get translated (in a reversible way) a set of legal characters in the new spec. -Tad -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
