Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>I thought the whole point of sessions was to authenticate users. </p> </blockquote> <p>No, sessions are used to identify requests that belong to the same browser. It does not identify or authenticate users. This is the job of your code. Sessions usually work via Cookies: on first request servers sends a cookie, then on all subsequent requests browser adds cookie to the request. That's how server knows that a series of requests belong to the same client (browser). For this to work in your case, your <a href="https://stackoverflow.com/questions/3587254/how-do-i-manage-cookies-with-httpclient-in-android-and-or-java">Android code should use cookies</a>.</p> <blockquote> <p>Isn't there supposed to be some id?</p> </blockquote> <p>Yes, after login you'd normally get some user ID, but this is specific to login procedure. Also this has nothing to do with sessions. Session is basically an object on the server side that is always the same when requests come from the same client. You can store some attributes into the session object: normally after user performs login, you'd store their user ID into session to easier identify requests coming from the same user. When user logouts, you'd delete the user ID from session.</p> <blockquote> <p>What do I send back to the client after a successful login?</p> </blockquote> <p>Enable sessions on server (= <a href="https://github.com/dound/gae-sessions/wiki/comparison-with-alternative-libraries" rel="nofollow noreferrer">pick your library</a>) and <a href="https://stackoverflow.com/questions/3587254/how-do-i-manage-cookies-with-httpclient-in-android-and-or-java">enable cookies in Android code</a>. Then sessions will be automatically handled between your client and server. After successful login just store user ID into session. On subsequent requests just check if session contains user UD.</p> <blockquote> <p>How does get_current_session know who the user is?</p> </blockquote> <p>It doesn't. After login you store some user-related data into session and on subsequent requests you can check for this data.</p> <blockquote> <p>What does the client send to the server with every request?</p> </blockquote> <p>For sessions to work it should send a cookie. This is done automatically if you enable cookie support in Android HttpClient code (link above).</p> <blockquote> <p>What if the user is signed in from multiple devices?</p> </blockquote> <p>Multiple clients would result in multiple independent sessions. It's up to your server code to identify sessions that belong to same user (= multiple sessions would have same User ID stored in them). </p>
    singulars
    1. This table or related slice is empty.
    1. POUsing sessions in Google App Engine with mobile client
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPeter Knego
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing sessions in Google App Engine with mobile client
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CONitpick: You really ought to quote quotes, rather than putting them in code blocks.
      singulars
      1. PO
      1. USNick Johnson
    2. CONow how does this work with a mobile application - do sessions treat an app like a browser? Theoretically, what would happen if the user has a session, but deletes the app and reinstalls it - will the session still be valid - why or why not? (I know I can easily test this, but I want to understand *why*)
      singulars
      1. PO
      1. USSnowman
    3. COSessions are (mostly) based on cookies, which browsers automatically handle (and persist to disk). In your app you need to handle cookies in your code. `BasicCookieStore` class helps you with this, but afaik it's memory based, so it would loose session info between restarts and reinstallations. If you need something different that survives restarts you should create your own version by extending 'CookieStore`: http://developer.android.com/reference/org/apache/http/client/CookieStore.html
      singulars
      1. PO
      1. USPeter Knego
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload