Loop/Architecture/MVP: Difference between revisions

Loop/Architecture/MVP (view source)

209 bytes removed , 18 July 2014

→‎Transition: Explain why MLP and MVP are not compatible anymore.

68

edits

@@ Line 461: / Line 461: @@
 === Transition ===
-It is possible to implement this transition without moving to a different set of servers; and without requiring a "flag day" on which all old URLs stop working. Our current tokens are on the order of 200 characters in length, while the new tokens are 11. If a token is longer than some break-over point, say 80 characters, it can be interpreted as an old-style token (information is extracted directly from the token). If it is shorter than that, then it is assumed to exist in the URL token table, and is looked up there instead.
-This is, of course, temporary: after a 30-day period, this functionality can be removed, as all old-style URLs will have expired by that time.
+MLP and MVP version are not compatible.
+Since there is only nightly users on MLP (Loop 0.5.0) and that it only handle call-url, all old call-url will stop working and defined as expired.
+During the transition from MLP to MVP all old user will have to recreate call-url in order to get the new format.
+The initial plan was to have both URLs working during a month to smooth the transition but it doesn't worth it with regards to the number of existing call-urls.
 == Advanced Call Handling ==