Flash Response Direct

Question

0.00/5 (No votes)

See more:

Hello,

I have a site that goes from ASP.NET to FLASH and BACK.
I use response.redirect to get from ASP.NET to FLASH.
AND I use getURL+vars to get back to ASP.NET page.
When I try and go back to ASP.NET page using chrome you can see a percentage counting up to 100% in the bottom left hand corner of browser. My question is, why does it do this and what causes it to be fast or slow? And are there ways to make it go faster?

Posted 10-Feb-13 15:39pm

GreenKhan

Updated 10-Feb-13 15:40pm

Andreas Gieriet

v2

Add a Solution

Comments

Andreas Gieriet 10-Feb-13 21:43pm

I did remove the shouting title.
On topic: did you try to monitor the traffic, e.g. with a packet sniffer?
Cheers
Andi

GreenKhan 10-Feb-13 21:53pm

On the flash end? I monitor things using LOCAL HOST, but when doing it online, Im not sure what causes the speed to slow when coming back from FLASH to ASP.NET. Never heard of a pack sniffer? Whats the best way to go about doing that?

Andreas Gieriet 10-Feb-13 22:59pm

Go and get http://www.wireshark.org/.
It's a packet sniffer that shows that data pssed by what time.
So, you should get an idea on server side when and what goes in/out of the socket in question.
Neets some initial learnig on how to filter and read the data. Debugging network issues is never for free... ;-)
Cheers
Andi

GreenKhan 10-Feb-13 21:57pm

Is that percentage for loading time to do with the FLASH file sending something OR the ASP.NET page loading? Cause when I send to a simple ASP.NET page it loads faster.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)