forums.smartfoxserver.com

Hi,
while the board is disseminated with small hints about the next major release we haven't made a public announce yet, the work being done is massive and we have no release dates set as of now.

Also--I really think you need to include an encryption option on the server as well. Maybe you can request a public key on the server, much like you can request a random number. And then use that to encrypt/decrypt all the traffic.

I'd say encryption yes
Encrypting all the traffic no (or at least, not recommended at all)
With a binary protocol decoding traffic decryption it's not going to be an easy task and encryption (proper one) costs some good server performance and should be used with parsimony (or big multi-cores )

Just checking on the outlook for this.

There are hints that the "binary protocol" is AMF? is that so?
I've been using Red5 for a year or so (it is AMF/RTMP based)
If I want "binary protocol" (to send images to client)
should I just make a NetConnection to Red5?
(and use Red5 api to talk to SFS api on the Java side)
If I run the app through Red5, is there value to directing into SFS,
and having SFS call back to my extension? vs just staying in Red5 "rooms"?

also, with regards to encryption, i do not believe that should take massive cpu power.
Maybe look at how SRTP (as used by SIP and other IP media) does it.
Basic just calculate a random bit sequence and XOR it to the packet data.
Both ends agree on a protocol to rotate the 'keys' (the random seeds)
so this it not more computationally difficult than a random number generator.
(and there are block-sequence generator just for this purpose)
Voip servers commonly serve hundred of 50-100 kbps channels with SRTP.

There are hints that the "binary protocol" is AMF? is that so?

We are not going to use AMF. Actually the next protocol will be more efficient and better performing than AMF.

I've been using Red5 for a year or so (it is AMF/RTMP based)
If I want "binary protocol" (to send images to client)
should I just make a NetConnection to Red5?(and use Red5 api to talk to SFS api on the Java side)

No, because Red5 doesn't run in the same JVM with SFS.
You can easily upload images via normal HTTP and SFS supports FILE_UPLOAD events. You can find more details in the documentation with a full example (Image Manager)

also, with regards to encryption, i do not believe that should take massive cpu power.

We are going to use public-key based encryption.