I am trying to handle a situation where my user are getting
temporarily disconnected from my web app and then proceeding to
continue enter info thinking that it is being saved simply because it
is still working in actionscript. (of course nothing is getting
persisted to the database at this point). This problem seems very
unique to data management since we are not making explicit calls to
the database and instead it is being handled by DataServices.
I have tried to set up an Alert warning and a status indicator so that
they know when then are connected again, however, sometimes I am
getting the follow error when the web app is reconnected (see below).
Admittedly this usually happen when there is a server restart
(although is there a way to check for this?), but I am still wondering
how best to manage my apps connection since I am not doing explicit
asynchronous calls to the database?
Thanks for the help. - Kevin
[RPC Fault faultString="Pages for sequence id 209 have expired in
destination relationships." faultCode="Server.Processing"
faultDetail="null"]
at
mx.data::ConcreteDataService/http://www.adobe.com/2006/flex/mx/internal::dispatchFaultEvent()[C:\depot\flex\branches\enterprise_bridgeman_final_hotfixes\frameworks\mx\data\ConcreteDataService.as:2112]
at
DataListRequestResponder/fault()[C:\depot\flex\branches\enterprise_bridgeman_final_hotfixes\frameworks\mx\data\ConcreteDataService.as:6022]
at
mx.rpc::AsyncRequest/fault()[E:\dev\flex\sdk\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:103]
at
NetConnectionMessageResponder/statusHandler()[E:\dev\flex\sdk\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:531]
at
mx.messaging::MessageResponder/status()[E:\dev\flex\sdk\frameworks\projects\rpc\src\mx\messaging\MessageResponder.as:222]
