unsubscribe
On Thu, Mar 22, 2012 at 1:42 AM, Hudson (Commented) (JIRA)
wrote:
>
>[
> https://issues.apache.org/jira/browse/THRIFT-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13235452#comment-13235452]
>
> Hudson commented on THRIFT-1532:
> -
does not supply any threadsafe area. You have to use an object
> pool or ThreadLocal variable, etc.
>
> On Tue, Sep 20, 2011 at 4:27 PM, Marty Weiner wrote:
>
>> Ah ok. It is multithreaded and concurrent requests are allowed. Is there
>> a threadsafe area to allocate from? I
gt; so, then you can't declare just a single list in your handler. Handler
> access is not threadsafe.
>
> On Tue, Sep 20, 2011 at 11:01 AM, Marty Weiner wrote:
>
>> Ah, sorry, I should have been clearer. This is from the server end.
>>
>> Some other thread ca
ot; reservation mechanism? ThreadLocals?
>
> On Sat, Sep 17, 2011 at 12:02 AM, Marty Weiner
> wrote:
>
> > I'm trying to understand (what I think is) a bug in the generated java
> > code. My thrift schema generates this method:
> > public List listGet(String key) thr
I'm trying to understand (what I think is) a bug in the generated java
code. My thrift schema generates this method:
public List listGet(String key) throws org.apache.thrift.TException {
... }
To avoid an allocation on every listGet request, I'd like to keep a
pre-allocated List buffer per thread
