I do have a product that has been tested with iOS 5 and so far there does not seem to be any issues with the latest iPhone API from around the time of RC 2 release.

Lapo,

Thanks for all support. Just to let you knwo that the SFS iPhone API do compile for Mac OS projects with a few minor tweaks of BitSwarmClient.m and SmartFoxPhoneClient.m . If you are interested I can sent you the tweaks.

It is the responsibility of the SFS Client to keep proper state. how come the low level BitSwarm protocol indicates it is connected when the SFS Client says it is not. This had nothing to do with handling states of the application. There is messed up code in setting uo properties for the SFS Client.

Hi I have a box with 2x4QUAD CORES with 12GB of RAM and expected 5K users at any time. What is the optimal server settings, like memory and various pool sizes. I use custom Java extensions extensively.

It had solved, frozen users issue.

I run into the same issue with Zone files. It turns out that the Main class parameter can not be properly filled in the Admin interface. adding the parametr <file> in the zone file manually fixes it for me,

It has been a while since I had asked if possible to add a Force Kick (force close user sessions) fro with in the admin. Every time a user get stuck I have to reboot the server and kick everyone out in the process. Come on guys it should not be that hard. You have the thread identified just add seve...

Actually on the Mac you get IOStream error even with idle connection. So that can be handled and the sessions reestablished on a new socket. I have done work on a successful socket jumper we called it. If you are interested I can help with that in SmartFoxServer.

I undersand the SmartReconnect mechanisms does not cover cable unplugged scenarios on the client side. Do you have plans to allow a session to be moved on a different socket, very useful to reconnect iPhone / iPad . Those have the tendency to switch to 3G fro Wifi without apparent reason.

The increase on the interval is not much of a solution as if you keep the client at the login box for two minutes then you run in the same issue. I have found a temp work around for my self but it is not too good. I connect my client and let it sit connected without login. On the server console I se...

After further investigation I don't see any data passed to the client when the server removes the session. There should be a termination byte sent in so that the iPhone client knows to close it's socket too.

I run in the following issue: I connecte the client and a login box is displayed. My authentication time out is 20 seconds. If the user does not login in 20 second I do see the server closing the connection. When SFSClient is check _isConnected=NO and when the BitSwarn is checked it shows connected=...

I had been running SFS in production environment, and not such problem manifested it self.

How does you custom authentication works?

That is the big problem no SFS events are fired what so ever. Please check the client with the procedure I have described.

I do agree with all you have said, but never the less I have to get some indication from the SFSClient of it's state. If you just send the app to the background and do not lock the screen the connection never gets dropped and once the app is called to foreground it continues working as a charm. Howe...