I logged an issue with ring, and they told me that web servers can't enable knowing about the same tab refreshing because browsers don't expose tab identities.
I resolved to just use (session|local)Storage. I think that's the only way to isolate identity down to the tab level but also persist identity across refreshes and pageloads. Thanks Dan for commenting on mah sente issue! :) On Saturday, March 28, 2015 at 6:58:50 PM UTC-4, Dillon Forrest wrote: > Hi Colin, just curious, but have you been able to figure out your Sente issue? > > Upon second reading, I realize my issue is different and much less complex > than yours. I just want to uniquely identify 1 tab in 1 browser on 1 device, > but have that id persist across user refreshes or clicking links or anything > which will prompt a second initial socket handshake within the same tab. I > still can't figure it out though. D: Does anybody have any ideas? > > (logged my own issue here: https://github.com/ptaoussanis/sente/issues/118) > > Sente creator Peter Taoussanis has been very awesome and patient though. He > suggested logging a github issue with questions! > > > > On Friday, March 27, 2015 at 1:45:51 PM UTC-4, Dillon Forrest wrote: > > hahaha i'm all about that :) > > > > > > > > > > > > > > > > -- > > i blog about starting a company here > > > > i also host a podcast > > > > > > On Fri, Mar 27, 2015 at 1:43 PM, Daniel Kersten <[email protected]> wrote: > > > > We should start a club for people who will be kicking themselves :) > > > > > > On Fri, 27 Mar 2015 at 17:07 Dillon Forrest <[email protected]> wrote: > > Hey Colin, as a crazy coincidence, I'm trying to accomplish something very > > similar. I started wondering if I should set a session uuid server-side, > > but I'm sure there's a more elegant solution out of the box. Also expecting > > to kick myself once I know the correct way to do it. :) > > > > > > > > On Friday, March 27, 2015 at 4:52:44 AM UTC-4, Colin Yates wrote: > > > > > I did try that but then I can't find where to access that in the messages > > > received from a client. I know I am going to kick myself... > > > > > > > > > > On Friday, 27 March 2015 00:54:46 UTC, Wei Hsu wrote: > > > > > > If you want each client to be unique, what if your user-id-fn could > > > > just generated a UUID? > > > > > > > > > > > > On Thursday, March 26, 2015 at 9:19:11 AM UTC-7, Daniel Kersten wrote: > > > > > > > I actually would like to do the same thing. For authentication, I > > > > > would use a JSON Web Token and would happily pass that with my > > > > > requests manually. I don't care if client id's change because my > > > > > server is stateless-REST-like. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, 26 Mar 2015 at 15:22 Colin Yates <[email protected]> wrote: > > > > > > > I have read the documentation but I think I am having a bad day as I > > > > > just can't get it to click. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Essentially I would like each new 'client' to be uniquely identified > > > > > where: > > > > > > > > > > > > > > - a new client is created for every 'client-less' request (e.g. a > > > > > new tab) - each subsequent request is then associated with that client > > > > > > > > > > > > > > - server restarts can happily drop all existing clients and they can > > > > > become new clients > > > > > > > > > > > > > > - authentication is handled elsewhere > > > > > > > > > > > > > > > > > > > > > > > > > > > > I can't use the ring's session-id as it is shared by every tab. I > > > > > notice a 'client-id' which appears to be unique across tabs but the > > > > > FAQ implies that 'client' is the wrong granularity. > > > > > > > > > > > > > > > > > > > > > > > > > > > > I am sure I am being a numpty, but what do I need to do. Is a > > > > > user-id-fn of :client-id sufficient? > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > Note that posts from new members are moderated - please be patient > > > > > with your first post. > > > > > > > > > > > > > > --- > > > > > > > > > > > > > > You received this message because you are subscribed to the Google > > > > > Groups "ClojureScript" group. > > > > > > > > > > > > > > To unsubscribe from this group and stop receiving emails from it, > > > > > send an email to [email protected]. > > > > > > > > > > > > > > To post to this group, send email to [email protected]. > > > > > > > > > > > > > > Visit this group at http://groups.google.com/group/clojurescript. > > > > > > > > -- > > > > Note that posts from new members are moderated - please be patient with > > your first post. > > > > --- > > > > You received this message because you are subscribed to the Google Groups > > "ClojureScript" group. > > > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > > > To post to this group, send email to [email protected]. > > > > Visit this group at http://groups.google.com/group/clojurescript. > > > > > > > > > > > > > > -- > > > > Note that posts from new members are moderated - please be patient with > > your first post. > > > > --- > > > > You received this message because you are subscribed to a topic in the > > Google Groups "ClojureScript" group. > > > > To unsubscribe from this topic, visit > > https://groups.google.com/d/topic/clojurescript/AZlkAACi7gc/unsubscribe. > > > > To unsubscribe from this group and all its topics, send an email to > > [email protected]. > > > > To post to this group, send email to [email protected]. > > > > Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
