Forums Register Login

Java RPC options

+Pie Number of slices to send: Send
Hi,

I am fairly new to java. Basically a C++ programmer.Have recently switched to java and need to implement something in my project.
My requirement is for a server to send some data continously to it's subscribed client and also to provide this data when clients request for it on adhoc basis.
I want to know what are my options with Java.
I hear thrift and google protobufs are the way to go these days but don't want to go for it just because it is popular.Want to first understand if it suits my need.
Performance is a key for my project so the data should be pushed to the client as soon as it is availabe to the server.
so communication should be fast.And the data in the server is updated every few milliseconds throughout the day.I am still unsure about the size of the data.
Can someone tell why thrift and google protobuf is better than java RMI or message queues(JMS QPID) for RPC?.I really need to understand why people use thrift etc instead of message queues,RMI.

Thanks
+Pie Number of slices to send: Send
Why do you want to do this?

In general, 99% of the time you think you want a Java RPC, you are better off not using an RPC at all.

Instead, send a message containing data, receive it, process it, and return results data in a message back.
+Pie Number of slices to send: Send
Hi Pat,
Thanks .I have chosen JMS qpid with thrift serialization .
Cheers
Willie Smits can speak 40 languages. This tiny ad can speak only one:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 1395 times.
Similar Threads
RMI marshaling and unmarshaling
Design Suggestions
confusion on FBN
Awaiting the exam results
Design of data access layer - please comment on
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 29, 2024 08:30:47.