Mailing List
Home
Forum Home
Flash Pro
Subjects
Firework Effect
setInterval bug identified and fixed
setInterval bug identified and fixed
ScrollPane component doesn 't auto update
Help: MX 2004 How to script a print button to print the entire sli
Event Dispatcher between classes
memory management removeMovieClip /
MX2004 Dataset itemClassName
Order of events per frame
XML to Object help
Textfield prototype question
Flash and QuickTime VR
Reading and displaying RSS feeds in Flash MX
Flash MX 2004 Sucks
AW: [Flashcoders] Switch/Case vs If/else
AW: [Flashcoders] Switch/Case vs If/else
Flash Interface with 10mb xml file
Web Service Results
Listener Object 's best practice
 
Clients getting disconnected from FCS after idle time

Clients getting disconnected from FCS after idle time

2004-02-26       - By Jorge Maiquez

 Back
I first noticed it ages ago (FCS1.0 I think) in apps where no
connectionlight or any other pinging mechanism was being used. Haven't
really noticed it since, but then again most of my apps now make use of
some sort of pinging..
No big help, I know.. just a confirmation that I've also seen this
behaviour before, and I think it happened more with mac's than with
pc's, but don't hold me to that :)

Cheers,
-Jorge


Jorge Maiquez
Technical Architect

Digital Samba

C. Viladomat 108, Pral. 1a
08015 Barcelona
Tel.: +34 93 451 56 62
Mobile: +34 647 236 027
http://www.digitalsamba.com

This e-mail is intended for the named addressee only. It may contain
confidential and/or privileged information. If you have received this
message in error, please let us know and then delete this message from
your system. You should not copy the message, use it for any purpose or
disclose its contents to anyone.

-- --Original Message-- --
From: graeme.bull@(protected)
[mailto:graeme.bull@(protected)]
Sent: Thursday, February 26, 2004 7:51 AM
To: flashcomm@(protected)
Subject: RE: [FlashComm] Clients getting disconnected from FCS after
idle time


Hi Ed,

You're on fire or something! right on.  This is an old bug and most
people have got around it by using their own "pinging" function or
something.

I suggest just making a very simple application where you can press a
button and the server side will return a value and show it in a text
field.  Build, run it, test it and then leave it for about... 2 mins or
so and press that button again.  It's not so much that the client gets
disconnected, it's that the client on longer can send or receive with
the server.  Very strange.

(we have tried the maxappidle time too, see the archives if you need
confirmation, it's all there)

Graeme

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Supported by Fig Leaf Software
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Lower Prices for Certified Training! Check out new lower prices for
Certified Macromedia Training from Fig Leaf Software. Expand your
skill set with courses in ColdFusion, Flash, Rich Internet
Applications and .NET in the new year.  Fig Leaf Software provides
the highest caliber instruction at our training centers in Washington  
D.C., Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at
your location.

Get the details at http://training.figleaf.com/
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe, e-mail: flashcomm-unsubscribe@(protected)
For additional commands, e-mail: flashcomm-help@(protected)