Session Management for client and server

JS

unread,

Nov 3, 2015, 8:35:12 PM11/3/15

to grpc.io

Hello All,

Is there anyway the server maintains the sessions of client? or is everything defined in context of the client that gets connected?

Regards,

JS

Nathaniel Manista

unread,

Nov 4, 2015, 11:53:05 AM11/4/15

to JS, grpc.io

On Tue, Nov 3, 2015 at 5:35 PM, JS <jsmr...@gmail.com> wrote:

Is there anyway the server maintains the sessions of client? or is everything defined in context of the client that gets connected?

Tell us more about your use case? What would you foresee your server doing with client sessions if it were to maintain them?

-Nathaniel

JS

unread,

Nov 4, 2015, 3:05:17 PM11/4/15

to grpc.io, jsmr...@gmail.com

Hi,

My server needs to know which client its talking to. For say if there are any series of transactions that take place to the DB, it needs to keep track of the client session that made those changes.

Eric Anderson

unread,

Nov 4, 2015, 3:56:44 PM11/4/15

to JS, grpc.io

We would normally recommend using streams for modelling transactions.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5ab34732-de1d-4691-84bb-3bc3c7c6a289%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Louis Ryan

unread,

Nov 4, 2015, 7:50:32 PM11/4/15

to Eric Anderson, JS, grpc.io

Embed the notion of session into your API design (this is along the same lines as Erics comment) though you don't necessarily have to use streams.

Often this comes up when affinity between the client and server is not 'hard', e.g. in the case of a reverse proxy sending requests from 1 client to many backend servers. If your servers have a stateful session/txn model this becomes problematic and streams are a good way of solving this issue. If you can guarantee hard affinity then things are easier

On Wed, Nov 4, 2015 at 12:56 PM, 'Eric Anderson' via grpc.io <grp...@googlegroups.com> wrote:

We would normally recommend using streams for modelling transactions.

On Wed, Nov 4, 2015 at 12:05 PM, JS <jsmr...@gmail.com> wrote:

Hi,

My server needs to know which client its talking to. For say if there are any series of transactions that take place to the DB, it needs to keep track of the client session that made those changes.

On Wednesday, 4 November 2015 08:53:05 UTC-8, Nathaniel Manista wrote:
On Tue, Nov 3, 2015 at 5:35 PM, JS <jsmr...@gmail.com> wrote:
Is there anyway the server maintains the sessions of client? or is everything defined in context of the client that gets connected?

Tell us more about your use case? What would you foresee your server doing with client sessions if it were to maintain them?
-Nathaniel

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.

To post to this group, send email to grp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/5ab34732-de1d-4691-84bb-3bc3c7c6a289%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "grpc.io" group.

To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.

To post to this group, send email to grp...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CA%2B4M1oNYXJoCecGM-KwC2FNkGR6CCe%2B5RPD36QhMZNNCD6J29A%40mail.gmail.com.

Reply all

Reply to author

Forward