Hi Dirk,

 

The fill call should definitely be raising a fault event in this case.  We don’t have a way to set resubscribeAttempts…  Our thinking is that you can call “dataService.disconnect()” if you want to stop the data service from trying to subscribe.   The next attempt to execute a fill, getItem, etc. causes the connect attempts to start up again. 

 

The problem with supporting resubscribeAttempts is that if you remain connected and stop trying to subscribe because the resubscribeAttempts is reached, there is no way in the api to get it to try and subscribe again.  We did consider the idea of exposing the entire consumer api but it seemed like it made the api unnecessarily complicated.  

 

Jeff

 


From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Eismann
Sent: Tuesday, August 01, 2006 12:14 AM
To: [email protected]
Subject: [flexcoders] Set resubscribeAttempts on DataService?

 

Is there any way to set the resubscribeAttempts of the underlying
Consumer instance used by a DataService?

In the case where the remote destination endpoint is not accessible
(i.e. network or server down) an attempt to connect to the destination
by invoking a fill() operation neither fires a fault event, nor do I get
a timeout (requestTimeout is set on the DataService) but just runs
forever.

Looking at the output of TraceTarget I see that the DataService's
consumers attempt to subscribe again and again but this never stops
automatically.

Any ideas?

Dirk.

__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to