OK, I think what we need to do then is make some Thrift-wide
decisions about what a library should provide, and then create JIRA
tickets for each of these features, with sub-issues for languages
that don't have the right features.
Should we just discuss these features in this thread, or is there a
better approach?
-Bryan
On Mar 10, 2009, at 3:01 AM, Franis Sirkovic wrote:
I see library unification as a big problem.
I have used C#, Python and Erlang libraries and there are significant
differences between them. I suppose other libraries are different too.
For example, Erlang server will disconnect after 10 seconds (hard
coded in
source) and Python server will wait forever.
You can stop C# and Java server (they have Stop() methods). Keyboard
interrupt is only way to stop Python server (I didn't find other
way).
Erlang server has stop "method", but you stop only listener. Client
connections will stay alive forever.
Also, there is no way to customize C# or Java servers. There are
just public
and private members. I think that there should be a way to
customize classes
in all languages. For example, I have this problem because I need
notification when connection is broken. Of course, couple of standard
methods in Handler interface (new_client(), closed(), ...) can
solve this
problem. Or, maybe better, just one notify() method that will
receive all
notifications (like Erlang handle_info() function).
Best wishes, Franis.
