Jussi's 10Centuries Playground

@matigo I would assume so, as that behavior is needed to allow a user to log in from the same app on two separate devices, right?

@matigo If a user logs in again without logging out in between, the API returns a new authorization token?

Ha! Login works, login works! Insert evil laughter here.

@c It's all ~4–6 mm long, so no…

Tearing my head off because of a bug that happened mostly during the weekend and cannot be reproduced anymore. Some days I just hate my work.

@matigo @konrad I think I will use the 3rd-party library. Just to make things easier for me.

@konrad Well, I am writing an app for 10Centuries, so maybe. :-)

@matigo Most likely the wrapper I would write would not get that easily out of date. The SQLite access layer isn't bound to change that often. That 3rd-party library I've been eyeing (and using in other projects) has changed some of its API quite dramatically during the past 12 months. But it would make things a lot easier, though…

Hmm… To use a 3rd-party library to handle the database or to write my own wrapper for the SQLite access, that's the question of the day. If I use the library, the code will be much, much easier. But then again, that's a 3rd-party library I need to keep updated. Decisions, decisions…

To code or not to code. The 10C app, that is, not the day-job app.