I'm having serious issues surrounding timeouts in FDS. I tried setting the timeout for the rtmp channel to 60 and then the individual destinations to 60 as well, but I find my app loses the connection long before then. The silly thing is that when I lower this value to 10, at least the client gets a disconnect event that I can code against. This solution works about 60% of the time. Setting the values to 0 actually makes things even worse.
Having said that, is there any way that anyone has figured out to actually get the connection to NOT time out? The application we are building is a chat application, and while people are chatting, sometime in the middle, suddenly the data services disconnect, causing odd behaviour and lowered confidence in the product. I realize the disconnect might be network related, however it seems odd that I can't trap this disconnection event on the client side. I monitor every single event on my dataservice, and there just is no event to speak of... I'll go to create a record using createItem and it will save to the db, however the datagrid showing these records will not update. Sure I could use addItem instead but that still doesn't solve to problem for other clients that are monitoring the same dataset. This also affects messaging. When a producer fails, Flex is smart enough to reestablish a connection, but a failed consumer doesn't just suddenly start listening again. In fact, both running inside the same client will still display this terrible reality... the user can still send messages but can no longer see the messages they have typed in, nor can any other consumers that have for some reason or another lost their connection without warning. Help!
