English 
Español
한국어
print pageMonitoring HTTP Traffic
This is the last of the client-side approaches to debugging a ZoomFlex application. It involves using software that monitors all HTTP requests and responses between your machine and remote servers.
A typical case for using this type of debugging would be when you find that no results are being returned from the server after a delegate in a ZoomFlex application makes a server-side call. Another case of using this would be when you find that images are not loading up in your ZoomFlex application
An HTTP traffic monitor indicates the details for each request being made to remote servers over HTTP. This can include the URL requested, query parameters, cookie information and so on. HTTP monitors also display the results that come back in response to each request. Results can include the content returned, e.g., HTML, XML, AMF, cookies served etc.
We use an HTTP monitor called Charles and find it very useful in helping us debug tricky issues. An additional advantage of using Charles is that it supports the deserialization of the AMF packets. As you might know, Flex uses the AMF format to tranfer data between a client application and a server. AMF is a binary format that compresses information being sent between client and server, making the data transfer over the wire much quicker. A software like Charles can decompress AMF packets and show their contents.
Next approach: Unit Testing »
Comments
There are no comments for this page as yet.
Full RSS
