Re: [Php-java-bridge-users] PHP/Java Bridge 2.0 snapshot

[Jost B. <jos...@ya...>]

 
> PHP bug, an object destructor was called after
> module shutdown

Yes (it's a PHP bug, not a bug in the bridge). There
are a number of tickets regarding this problem.  I
don't know if or when the PHP people are going to fix
it.


> JavaBridge is quite slow - over 2 seconds in making
> 100 strings objects 

Depends on the network latency.  If you talk to the
server via a slow network with ~2ms latency, this is
feasible. For local sockets (either TCP or Unix
domain) the new protocol makes the bridge at least two
times faster.  From what I have seen the bench now
executes twice as fast as before: ~11s vs. ~4 seconds
native java code. 


> - is this normal behavior ?

Certainly.  Every RPC protocol has this problem. 
That's why one normally creates "value objects" on the
client-side and then sends these to the server. 
Bandwith is not the problem, latency is.

One could invent techniques such as "reply cookies" to
minimize the number of roundtrips.  But this is not
worth it, imho.  If you use local sockets, the
communication is reasonably fast.  If you want to talk
to a remote server, use value classes to communicate
with it.


Jost


	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 250MB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de