this is may a litle bit early question but iam acctually thinking of 
making red5 working together with other servers.

thatfor i asked myself what would be the best solution that would give a 
perfect performance.

i read in the roadmap about XML-RPC and XML-Sockets for version 0.7 are 
planned to be added to the featurelist and thought may it would be the 
best solution to use a internal interface in red 5 as soon as the xml 
rpc classes are added, but iam not sure what will give better 
performance and better results a socket or xml - rpc (iam here talking 
about server to server communication, not client server, the usage 
should be exchange of important datas (userdatas and messagedatas (XML) 
aswell)), a socket would be very uncommon for that, wouldent it?

there would also be a way using just the different servers as standalone 
and just depend on the same database for userdatas, but i wrote myself a 
few versions of socketservers in java escpeccially for the use with a 
Flashclient and the problem in that case is that java needs a \0 
(nullbyte) as a message terminator, when reading the streambuffer by 
line, if flash hangs up, disconnects for some reason(maybe usual due 
(24h)timeperiod by provider ) or if the java server for any other reason 
does not receive the terminating \0 the server stys listening to the 
client and the threads doesent stop or pause which causes the server 
former or later to die. i also tried it with bitwise reading the buffer 
which worked as far as there is no presistent datastream(a bigger file 
for example) than the performance is useless because u need to check the 
bufferlength, the string inside for a valid termination, delete the part 
of the string that was a message , if the bufferlength doesent change 
for a few seconds and there is no finished message transmission 
terminating inside the buffered string u need to ping the client wheter 
by IP wich may delivers wrong results or due a custum(webapp to client 
call) function u call on clientsite(eg. PING-PONG),  just to prevent a 
silently dying server.

in that case and also because i dislike the idea to open "2 socket" for 
each client, i would preffer a server to server interactive solultion 
and use just one stream for all datas, like i said iam not sure which 
would be the best way.

It would be nice if others on the list give me some suggestion, may some 
inspiration aswell, well any kind of experience with the topic.

Greetz
Sascha

_______________________________________________
Red5 mailing list
[email protected]
http://osflash.org/mailman/listinfo/red5_osflash.org

Reply via email to