Re: [flexcoders] HTTPService return times Air vs Flash (Solved - Kinda)

2010-02-20 Thread Lee Jenkins
Lee Jenkins wrote:
  
 
 
 Web based flex applications seem to take magnitudes longer to return a 
 result
 than do Air based application. I've tried with HTTPService and URLLoader
 components and it is the same.
 
 I've created one small air application and one small web based flex app
 identical. Air app is almost instantaneous while the web page based app
 (Firefox) takes noticeably longer.
 
 My guess is that browser mechanics (security, etc) is the culprit.
 

It always turns out to be the small things.  Turns out that using localhost in 
the url of HTTPService (or URLLoader) was the problem with Firefox.  Replacing 
localhost with my development computer's ip address removes the delay.

Judging from the status bar messages of Firefox when making a call using 
localhost, Firefox is resolving localhost on every request, resulting in a 
average (subjective) delay of 250 to 500ms before the request hits the server 
(which I wrote and can debug/break point).  Changing the URL fed to HTTPService 
to using the IP address resolves the problem.

--
Warm Regards,

Lee



[flexcoders] HTTPService return times Air vs Flash

2010-02-11 Thread Lee Jenkins

Web based flex applications seem to take magnitudes longer to return a result 
than do Air based application.  I've tried with HTTPService and URLLoader 
components and it is the same.

I've created one small air application and one small web based flex app 
identical.  Air app is almost instantaneous while the web page based app 
(Firefox) takes noticeably longer.

My guess is that browser mechanics (security, etc) is the culprit.

Any suggestions or comments?

Thanks,

--
Warm Regards,

Lee


Re: [flexcoders] HTTPService return times Air vs Flash

2010-02-11 Thread Lee Jenkins
Lee Jenkins wrote:
  
 
 
 Web based flex applications seem to take magnitudes longer to return a 
 result
 than do Air based application. I've tried with HTTPService and URLLoader
 components and it is the same.
 
 I've created one small air application and one small web based flex app
 identical. Air app is almost instantaneous while the web page based app
 (Firefox) takes noticeably longer.
 
 My guess is that browser mechanics (security, etc) is the culprit.
 
 Any suggestions or comments?

I take this back.  My mistake and should have checked it before posting, but 
the 
truth is that Air applications run from the IDE are magnitudes faster that web 
page based flex app run from the IDE.  When testing response times with the 
COMPILED web based flex app OUTSIDE of the IDE, the difference was noticeable, 
but negligent.

--
Warm Regards,

Lee


Re: [flexcoders] HTTPService return times Air vs Flash

2010-02-11 Thread Lee Jenkins
Lee Jenkins wrote:
  
 
 Lee Jenkins wrote:
  
  
  
   Web based flex applications seem to take magnitudes longer to return a
   result
   than do Air based application. I've tried with HTTPService and URLLoader
   components and it is the same.
  
   I've created one small air application and one small web based flex app
   identical. Air app is almost instantaneous while the web page based app
   (Firefox) takes noticeably longer.
  
   My guess is that browser mechanics (security, etc) is the culprit.
  
   Any suggestions or comments?
 
 I take this back. My mistake and should have checked it before posting, 
 but the
 truth is that Air applications run from the IDE are magnitudes faster 
 that web
 page based flex app run from the IDE. When testing response times with the
 COMPILED web based flex app OUTSIDE of the IDE, the difference was 
 noticeable,
 but negligent.

OK, I'll get my head screwed on right today sometime.

It appears that its Firefox (3.5.7) that causes the delay.  Two test 
applications with exactly the same code.  One is deployed to AIR and the other 
to a basic webpage, letting FlexBuilder create the html page, etc.

SWF running directly in flash player:
  - Little to no difference, fast

AIR app (either in debug mode or not):
  - Little to no difference, fast

SWF running in Internet Explorer 8.0:
  - Little to no difference, fast

FireFox 3.5.7
  - Noticeably slower.

Everything including server is running local on my computer (3 Gigs of RAM, 
Vista 32bit) and just to be sure, I disabled all add-ins and plug-ins for 
Firefox and the result is consistently the same.  Using either a URLLoader or 
HTTPService to pull down xml, Firefox takes a while longer to send the request 
to the server, once the URLLoader or HTTPService sends methods have been 
called, 
  than the other methods mentioned above.

The server application is my own Delphi/FreePascal based server so I could set 
a 
break point on the socket creation line to see exactly when the server received 
the request from the flex application.  With Firefox (as opposed to Air 
application, Internet Explorer or running the naked swf file in Flash Player) 
the time it takes for the server to get the request is significantly longer 
(1.5 
secs on average subjective speed) thus providing an overall and significantly 
longer delay to process the request from click to response.


--
Warm Regards,

Lee



Re: [flexcoders] HTTPService return times Air vs Flash

2010-02-11 Thread Jochem van Dieten
On 2/11/10, Lee Jenkins wrote:
 Everything including server is running local on my computer (3 Gigs of RAM,
 Vista 32bit) and just to be sure, I disabled all add-ins and plug-ins for
 Firefox and the result is consistently the same.  Using either a URLLoader or
 HTTPService to pull down xml, Firefox takes a while longer to send the request
 to the server, once the URLLoader or HTTPService sends methods have been 
 called,
  than the other methods mentioned above.

Did you disable the feature where Firefox checks an online list of
reported attack / forgery sites before connecting to a site?

Jochem


-- 
Jochem van Dieten
http://jochem.vandieten.net/


Re: [flexcoders] HTTPService return times Air vs Flash

2010-02-11 Thread Jake Churchill
I've been told that Firefox limits the amount of processor power that the
flash player plugin is allowed to use.  That may be your problem.  Perhaps
it also limits network usage/bandwidth.

I can't confirm this is true but your results seem to point that direction.

FYI, FF 3.6 was recently released.  Maybe try that to see if they have done
anything under the hood to help flash performance.

-Jake

On Thu, Feb 11, 2010 at 11:08 AM, Lee Jenkins l...@datatrakpos.com wrote:



 Lee Jenkins wrote:
 
 
  Lee Jenkins wrote:
  
  
  
   Web based flex applications seem to take magnitudes longer to return a
   result
   than do Air based application. I've tried with HTTPService and
 URLLoader
   components and it is the same.
  
   I've created one small air application and one small web based flex app
   identical. Air app is almost instantaneous while the web page based app
   (Firefox) takes noticeably longer.
  
   My guess is that browser mechanics (security, etc) is the culprit.
  
   Any suggestions or comments?
 
  I take this back. My mistake and should have checked it before posting,
  but the
  truth is that Air applications run from the IDE are magnitudes faster
  that web
  page based flex app run from the IDE. When testing response times with
 the
  COMPILED web based flex app OUTSIDE of the IDE, the difference was
  noticeable,
  but negligent.

 OK, I'll get my head screwed on right today sometime.

 It appears that its Firefox (3.5.7) that causes the delay. Two test
 applications with exactly the same code. One is deployed to AIR and the
 other
 to a basic webpage, letting FlexBuilder create the html page, etc.

 SWF running directly in flash player:
 - Little to no difference, fast

 AIR app (either in debug mode or not):
 - Little to no difference, fast

 SWF running in Internet Explorer 8.0:
 - Little to no difference, fast

 FireFox 3.5.7
 - Noticeably slower.

 Everything including server is running local on my computer (3 Gigs of RAM,

 Vista 32bit) and just to be sure, I disabled all add-ins and plug-ins for
 Firefox and the result is consistently the same. Using either a URLLoader
 or
 HTTPService to pull down xml, Firefox takes a while longer to send the
 request
 to the server, once the URLLoader or HTTPService sends methods have been
 called,
 than the other methods mentioned above.

 The server application is my own Delphi/FreePascal based server so I could
 set a
 break point on the socket creation line to see exactly when the server
 received
 the request from the flex application. With Firefox (as opposed to Air
 application, Internet Explorer or running the naked swf file in Flash
 Player)
 the time it takes for the server to get the request is significantly longer
 (1.5
 secs on average subjective speed) thus providing an overall and
 significantly
 longer delay to process the request from click to response.

 --
 Warm Regards,

 Lee

  



Re: [flexcoders] HTTPService return times Air vs Flash

2010-02-11 Thread Lee Jenkins
Jochem van Dieten wrote:
  
 
 On 2/11/10, Lee Jenkins wrote:
   Everything including server is running local on my computer (3 Gigs 
 of RAM,
   Vista 32bit) and just to be sure, I disabled all add-ins and plug-ins for
   Firefox and the result is consistently the same. Using either a 
 URLLoader or
   HTTPService to pull down xml, Firefox takes a while longer to send 
 the request
   to the server, once the URLLoader or HTTPService sends methods have 
 been called,
   than the other methods mentioned above.
 
 Did you disable the feature where Firefox checks an online list of
 reported attack / forgery sites before connecting to a site?
 
 Jochem

Hi,

Yes.

Tools  Options  Security

Unchecked:
  Block Reported Attach Sites
  Block Reported Web Forgories

(and restarted FF)

--
Warm Regards,

Lee