Short version of the question:
Is there any way in C++ Thrift to get the TServerEventHandler context into
a call on my server interface handler?
Long question + background:
I am running a daemon, and connecting to it with multiple applications,
all over AF_UNIX sockets. Each application has a
[
https://issues.apache.org/jira/browse/THRIFT-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13544095#comment-13544095
]
Jens Geyer commented on THRIFT-1815:
+1 for the patch (y)
There's just one minor
[
https://issues.apache.org/jira/browse/THRIFT-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13544099#comment-13544099
]
Andrew Gaul commented on THRIFT-1815:
-
Thanks; attached.
Code
[
https://issues.apache.org/jira/browse/THRIFT-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul updated THRIFT-1815:
Attachment: thrift-1815-compiler-line-buffering.patch
Code generators line buffer output
See https://builds.apache.org/job/Thrift-Compiler-Windows/463/
--
Started by an SCM change
Started by an SCM change
Building remotely on ubuntu4 in workspace
https://builds.apache.org/job/Thrift-Compiler-Windows/ws/
Checkout:Thrift-Compiler-Windows /
Add Destroy() call to your server interface. That way full lifecycle of
reverse connection is under client control.
void Destroy(1: string reverseConnectionInfo)
On 1/4/13 7:19 AM, Ben Craig ben.cr...@ni.com wrote:
void Initialize(1: string reverseConnectionInfo),
See https://builds.apache.org/job/Thrift-cpp/503/
--
Started by an SCM change
Started by an SCM change
Building remotely on ubuntu2 in workspace
https://builds.apache.org/job/Thrift-cpp/ws/
Checkout:Thrift-cpp / https://builds.apache.org/job/Thrift-cpp/ws/
If the applications were reliable, then that would work. They are not
though.
The applications in question are often in development, and they are killed
frequently. I don't want unexpected application death to manifest as a
memory leak in the daemon.
From: Troyanker, Vlad
I may have misunderstood your question. But to me your problem has very
little to do with thrift. The issue of safely recycling and/or destroying
connections has to be addressed in design. Thrift cannot solve connection
lifecycle issues. If all your clients are anonymous instances of the same
app,
[
https://issues.apache.org/jira/browse/THRIFT-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer resolved THRIFT-1815.
Resolution: Fixed
Fix Version/s: 1.0
Committed.
Code generators line
Thrift knows when the application - daemon connection goes bad. I can
even get those notifications with TServerEventHandler::deleteContext. So
I can identify my clients with the reverseConnectionInfo, and with the
context I create in createContext. I don't have any way to associate the
two
See https://builds.apache.org/job/Thrift-Compiler-Windows/464/changes
Github user andrewgaul closed the pull request at:
https://github.com/apache/thrift/pull/30
See https://builds.apache.org/job/Thrift-cpp/504/changes
[
https://issues.apache.org/jira/browse/THRIFT-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13544350#comment-13544350
]
Tim commented on THRIFT-1787:
-
You don't need to install a different version of java. Just
[
https://issues.apache.org/jira/browse/THRIFT-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13544381#comment-13544381
]
Hudson commented on THRIFT-1815:
Integrated in Thrift #599 (See
16 matches
Mail list logo
