SmartFoxServer 2X

[ernivan]

hi

will it support as2 client api ?

when it will be released ?

thanks

[Lapo]

There will be no support for AS2.
The server speaks a fully binary protocol and AS2 is too old to support it
Actionscript 3 is required.

As regards the release date, we are already in private beta and I think it will be out at the end of summer 2010

[ernivan]

after final SFS 2 release , will I buy SFS 1.x ?

[Lapo]

Yes, SFS PRO 1.x will continue to be available and maintained.

SFS2X is a far more advanced product, an it's also different from SFS PRO under various aspects, so it won't substitute SFS PRO.

[09op]

Please tell me I read this wrong, but did you say NO AS 2.0 EXAMPLES?

[Lapo]

I am saying that there will be no support for Actionscript 2.0, no API for the reason I explained before.

[ernivan]

hi

It will be great to add 3 different protocol (binary , text , rtmp) to the new version

[Lapo]

The SFS2X protocol is binary, largely more efficient than text and definitely more efficient than RTMP, which is proprietary. So no need for multi protocols.
More details here:
http://www.smartfoxserver.com/2X/protocol.php

[ernivan]

great !!!!

[Carl Lydon]

Will actionscript still be supported for server-side extensions? If so, does that mean it will be AS3, and if so, will it have AS3's speed boost compared to the AS2 extensions made for SF 1.x?

I realize that Java extensions are the way to go for ultimate speed and power, but I'm wondering if AS is still supported for quick prototyping, or for projects that are too small to justify the hassle and expense of Java coding.

[Carl Lydon]

I'm also wondering, if the compression of messages mentioned here:

http://www.smartfoxserver.com/2X/protocol.php

provides any additional protection against port sniffers? I imagine that the decompression algorithm is common and not a secret, but maybe it would make it just a little bit harder for a casual hacker to examine messages?

[Lapo]

Sorry, no more Actionscript on the server side. Python will remain because it integrates much better with Java.
Of course you will still be free to add the Rhino interpreter (as well as Ruby or any other JVM scripting language) in your extension and use your favorite language for prototyping.

Honestly I think that when you'll play with the new Java framework and deployment system you won't even think to go back to Actionscript
So many things have been improved and the main one is Java itself which since version 5 and 6 has become a much nicer language

[Lapo]

provides any additional protection against port sniffers? I imagine that the decompression algorithm is common and not a secret, but maybe it would make it just a little bit harder for a casual hacker to examine messages?

Well yes quite a lot. The protocol is not text anymore, even when in clear it's quite a pain to decode. When compressed is pure nonsense.

We have a long a in-depth discussion on a possible encryption feature, which probably won't provide so many benefits as it may sound, but still nice to have --> viewtopic.php?t=7839

[Carl Lydon]

So, with the Rhino interpreter, you can write in javascript, yes? And that's very similar to the javascript/as1 extensions? Would the old javascript/as1 extensions from sf1.x work in sf2.x if Rhino is working?

I'm asking because my java skills are not great, my main way of working was to make my extensions in as1 them translate to java.

[Sappho]

Lapo will the client API sourcecodes for the SFS2X be available? I know its precompiled swc in beta so i am wondering if it will be available in the final release its ultimately better to work with an api where you can access the source codes directly and even make small changes when necessary.