DonsProxy HowTos

Application HowTos

These examples assume you already know how to Start the GUI

With the GUI, you can:

• Watch traffic between your browser and the web application you're writing.
• Find out what your server application is really sending back.
• Watch remote calls made by your server
• Simulate slow connections. Do you have users that access your application over a satellite link? Do you have users with old, slow modem connections? You can simulate slow connections, and see your application as your users see it.
• Watch SOAP traffic.
• Watch RESTful calls.
• Watch AJAX applications communicate.
• The "hard" work of storing application traffic as XML is already done. You can process this XML to analyze network traffic. Are your caching policies set to cache everything that should be cached? Run the CachingSummary analyzer to summarize caching behavior, and see what's being cached and what's not. What makes that web page take so long to load? DonsProxy will show you what parts are slow to load.

Coder HowTos

• Capture traffic and store it as XML. You can process the XML to create scripts for load simulation, integration testing, and more.
• Connection behavior modification is implemented using the Decorator pattern - this means you can easily write your own Decorator to modify connection behavior to your liking. The LatencyDecorator is done with just a few lines of code! Your Decorator can work in concert with existing Decorators. Packet traffic is fed from the core proxy engine to Subscribers. You can write your own Subscribers to view any protocol - LDAP, JDBC, whatever.
• You can include DonsProxy in your product. Say you're IBM, and still including TCPmon with WebSphere. You could be including DonsProxy instead, and getting so much more functionality. Just sayin'.
• Write your own parser to parse HttpXmlSubscriber output. Model your analyxer after CachingSummary.java.