Fossil SCM
Removed the "Multiple logins per user" caveat from the JSON API intro doc: that restriction was due to the IP address in the cookie, which is now long-removed.
Commit
40715d84bc430e5623ae062538f0a051927ca78b17ce9409ce1f7d88ac88eaee
Parent
0f20b5379414a2d…
1 file changed
-21
-21
| --- www/json-api/intro.md | ||
| +++ www/json-api/intro.md | ||
| @@ -171,26 +171,5 @@ | ||
| 171 | 171 | hindsight, we might better have used a higher-precision time format, |
| 172 | 172 | but changing that now would break API compatibility.) |
| 173 | 173 | - **Artifact vs. Artefact:** both are correct vis-a-vis the |
| 174 | 174 | english language but Fossil consistently uses the former, so we’ll |
| 175 | 175 | use that. |
| 176 | -- **Multiple logins per user:** fossil currently does not allow | |
| 177 | - multiple active logins for a given user except anonymous. For all | |
| 178 | - others, the most recent login wins. This is only a very minor | |
| 179 | - annoyance for the HTML interface but will be more problematic for | |
| 180 | - JSON clients. e.g. a user might have a ticket poller and a commit poller | |
| 181 | - running, and both would need to be logged in.\ | |
| 182 | - **Status:** as of 20120315 (commit | |
| 183 | - [*73038baaa3*](http://www.fossil-scm.org/index.html/info/73038baaa3)), | |
| 184 | - fossil allows a user to be logged in multiple times (confirm: only | |
| 185 | - within the same network?). The only caveat is that if any one of | |
| 186 | - them logs out, it will invalidate the login session for the others. | |
| 187 | - This is good enough for the time being, however. It will likely only | |
| 188 | - become painful if we actually get enough apps in the wild that | |
| 189 | - someone might have some running on his mobile phone and some on his | |
| 190 | - PC and some on his server. The workarounds for now are (A) not to | |
| 191 | - log out and (B) program apps/applets/widgets to try to re-login | |
| 192 | - occasionally. Fossil will at some point expire the login, anyway. | |
| 193 | - FIXME: update the expiry time on each request? To do that right we'd | |
| 194 | - have to re-set the cookie on each request :/. We could optionally | |
| 195 | - add a new JSON request which simply updates the login cookie | |
| 196 | - lifetime (e.g. /json/keepalive or expand /json/whoami to do that). | |
| 197 | 176 |
| --- www/json-api/intro.md | |
| +++ www/json-api/intro.md | |
| @@ -171,26 +171,5 @@ | |
| 171 | hindsight, we might better have used a higher-precision time format, |
| 172 | but changing that now would break API compatibility.) |
| 173 | - **Artifact vs. Artefact:** both are correct vis-a-vis the |
| 174 | english language but Fossil consistently uses the former, so we’ll |
| 175 | use that. |
| 176 | - **Multiple logins per user:** fossil currently does not allow |
| 177 | multiple active logins for a given user except anonymous. For all |
| 178 | others, the most recent login wins. This is only a very minor |
| 179 | annoyance for the HTML interface but will be more problematic for |
| 180 | JSON clients. e.g. a user might have a ticket poller and a commit poller |
| 181 | running, and both would need to be logged in.\ |
| 182 | **Status:** as of 20120315 (commit |
| 183 | [*73038baaa3*](http://www.fossil-scm.org/index.html/info/73038baaa3)), |
| 184 | fossil allows a user to be logged in multiple times (confirm: only |
| 185 | within the same network?). The only caveat is that if any one of |
| 186 | them logs out, it will invalidate the login session for the others. |
| 187 | This is good enough for the time being, however. It will likely only |
| 188 | become painful if we actually get enough apps in the wild that |
| 189 | someone might have some running on his mobile phone and some on his |
| 190 | PC and some on his server. The workarounds for now are (A) not to |
| 191 | log out and (B) program apps/applets/widgets to try to re-login |
| 192 | occasionally. Fossil will at some point expire the login, anyway. |
| 193 | FIXME: update the expiry time on each request? To do that right we'd |
| 194 | have to re-set the cookie on each request :/. We could optionally |
| 195 | add a new JSON request which simply updates the login cookie |
| 196 | lifetime (e.g. /json/keepalive or expand /json/whoami to do that). |
| 197 |
| --- www/json-api/intro.md | |
| +++ www/json-api/intro.md | |
| @@ -171,26 +171,5 @@ | |
| 171 | hindsight, we might better have used a higher-precision time format, |
| 172 | but changing that now would break API compatibility.) |
| 173 | - **Artifact vs. Artefact:** both are correct vis-a-vis the |
| 174 | english language but Fossil consistently uses the former, so we’ll |
| 175 | use that. |
| 176 |