Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For your second questions: </p> <p>the Referer is not secure, as mentioned in the comments.</p> <p>I hava a similar problem in my application and this is how it works for me.</p> <p>first, i hava a single-page app where all traffic goes through the socket, but thats not necessary. it should work with sessions the way you managed it, too.</p> <p>in nodejs onConnect I ask the backend if the user is authenticated and then store the userid into the socket object (socket.data) and also populate a hashmap to lookup sockets from userids directly.</p> <p>second, i use Redis and subscribe to a redis list from nodejs (<a href="http://redis.io/topics/pubsub/" rel="nofollow">see redis pub/sub</a>). the php backend pushes messages in this list with a userid to address the message. nodejs takes this message (e.g. a new news feed item), looks up the userid in the mentioned hashmap and sends it to the client. so, a user only gets what he is authorized for. the client then decides what to do with the message. if the user is on his feed page, it could add the item. if the user is on someone elses feed, it could simply add a notification somewhere else on the page. it might also discard it.</p> <p>on the php backend site, this messages are send to redis everytime an event occurs which needs to be shown live on some connected client. if user1 posts on user2's feed, the new item is stored in the database and in the same time is send as message into the redis queue.</p> <p>this system also helps to reduce DB load since nodejs just need to query a database to make sure the connected user is already authenticated.</p>
    singulars
    1. This table or related slice is empty.
    1. POPHP + socket.io (session, authorizing and security problems)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJan Prieser
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm not sure if I got it all correct: let's assume that we have 200 news feeds (or even make it 2000) that particular user can connect to. So whenever feed gets an update, we first need to check if the user can read that feed (that's a database query, but we can do it on the backside), then when we send him a message, right? The problem is, when user is looking at one feed, and at the moment 2000 feeds will get an update - node js will generate 2000 messages, but only one will not be discarded by the end-user. I think that is an overgrownth of sent messages... Or maybe I misunderstood?
      singulars
      1. PO
      1. USpatryk
    2. COmaybe i didn't understand your application. do a user gets live feed updates on every page he is visiting and have permissions? or only on his own feed page (like on facebook).
      singulars
      1. PO
      1. USJan Prieser
    3. COBasically it should be something like twitter, user wants to get socket.io messages only for pages he has currently opened (so, whenever he is on different browser tabs on page1 and page2 at once , the socket connected with page1 should get page1 updates, and socket connected with page2 should get page2 updates). That strategy will reduce number of messages sent - but the problem is need to redundand check database permissions (once for php backend to give page1 html and the other one is to check if socketio should send messages to the socket).
      singulars
      1. PO
      1. USpatryk
 

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