low latency connection

In low latency connection why do we prefer  RMI over IIOP and  Synchronous web service  invocation ?
cofactorAsked:
Who is Participating?
 
ksivananthConnect With a Mentor Commented:
>>failure ? why do you think so ?

because, in a slow connection, the possibility of timeouts is more based on the traffic... a slight increase in traffic will lead into more timeouts!
0
 
Gurvinder Pal SinghCommented:
Synchronous web service is a expensive process. See it this way.
1) at client side, Your proxy stubs (got using wsdl2java) will be serialized to xml soap request (unmarshalling, xml parsing)
2) xml will be deserialized to Objects at the server side (marshalling, xml parsing)
3) then corresponding method will be invoked on server side
4) its response will be serialized again at server side (marshalling, xml parsing)
5) deserialized again at client side to get the response in proxy objects (unmarshalling, xml parsing)

It naturally creates high latency. XML parsing is expensive

In case of IIOP also, the request is made in some format which needs to be marshalled and unmarshalled at both sides.


0
 
ksivananthCommented:
I don't think RMI-IIOP and low latency is in any way related for better thouroughput!

may be the preference is because of the additional overhead( data ) in RMI-IIOP

low latency prefered in synchronous comm because in a high lateny connection the possibility of failure in transferring the results is more which may seem the total request failed...
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
ksivananthCommented:
I can't think of the XML parsing impacts the latency because the parsing happens only at the client or server not in the network... shouldn't matter IMHO
0
 
Gurvinder Pal SinghCommented:
<<parsing happens only at the client or server not in the network>>
yes it happens only at client or server, but it is expensive. Just try marshalling a collection of more than 100 items, you will get to know the impact.

0
 
ksivananthCommented:
>>Just try marshalling a collection of more than 100 items, you will get to know the impact.

what I am trying to say is, the impact is on the client/server not in the network, the latency matters when the size of the data and the time it takes to transfer!
0
 
Gurvinder Pal SinghCommented:
It all adds to the latency.
When the web-service is invoked, all the 5 steps mentioned above happens. in those 5 steps i am not even including the network latency. It is extra.


0
 
cofactorAuthor Commented:
could you guys tell me what exactly low latency connection ? Can I call slow speed GPRS connection as low latency connection ? DSL Broadband as high latency connection ?
>>>high lateny connection the possibility of failure in transferring the results is more
failure ? why do you think so ?
0
 
ksivananthCommented:
>>in those 5 steps i am not even including the network latency

the question is just about network latency( why a low latency conn prefered for... ) not the other extra stuffs you mentioned!

the marshalling/unmarshalling, serialization/deserialization happens in async requests too... they are specific to client/server implmentation...
0
 
ksivananthCommented:
>>Can I call slow speed GPRS connection as low latency connection ? DSL Broadband as high latency connection ?

its the other way around, low latency is high speed!
0
 
Gurvinder Pal SinghCommented:
<<the question is just about network latency>>
Can you show that to me in the original question?
0
 
ksivananthCommented:
>>Can you show that to me in the original question?

read the question,

low latency connection Question: In low latency connection why do we
0
 
Gurvinder Pal SinghCommented:
Why am i not able to see "Network latency" in his question?
Are you saying latency is always related to network?

I agree with your point though that being 'Synchronous' is big part of the reason, which i missed.
0
 
ksivananthCommented:
>>Why am i not able to see "Network latency" in his question?

read the question fully,

>>RMI over IIOP and  Synchronous web service  

distributed applications communicate through a network.

>>In low latency connection

network connection for these apps!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.