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.

Reply via email to