People have asked for this in the past, and unfortunately we don't currently offer it. What kind of interface do think we should support? I'd love to see a patch for this (hint hint).
As a fallback, you could always make a custom Server implementation based off of one of the existing servers that doesn't use a thread pool in this fashion, which would let you use ThreadLocals. -Bryan On Wed, May 5, 2010 at 7:39 PM, Kenny MacDermid <[email protected]>wrote: > Is there any recommended way to store information about the connected > client in Thrift? > > I was looking to store the client information the way Cassandra does, using > ThreadLocal<> stores in the Server, but it appears this doesn't work. > Threads will be reused by the thread pool, so client information could be > reused. > > I'd like a way for clients to login() and not have to send a cookie back > with all future requests. Is this possible? > > Thanks, > > Kenny
