http://qs1969.pair.com?node_id=507347


in reply to Changes to the User Nodes ticker and introducing the NodeRep XML ticker

I don't personally use such things, but with the restriction on the interval between fetches, would it be possible to have some sort of "development" version that doesn't hit the db, but still spits out XML in the form that this ticker does? I know that if I were to create a client for this, I'd probably need more than 50 tries before the time restriction kicked in. Moreover, it'd be nice to continue development on such a thing and not have to deal with waiting 10 minutes in between authorized refreshes only to find that you forgot something.

thor

Feel the white light, the light within
Be your own disciple, fan the sparks of will
For all of us waiting, your kingdom will come

Replies are listed 'Best First'.
Re^2: Changes to the User Nodes ticker and introducing the NodeRep XML ticker
by Corion (Patriarch) on Nov 10, 2005 at 12:20 UTC

    When developing against web services, I capture the server responses to disk and replay them from disk. That way, I get exactly reproducible results and errors, and it also helps me to separate the gathering of input from the program logic, as I have to be able to easily replace a socket connection with a filehandle.

    If you're using any network based transfer and can install libpcap or Winpcap, using Net::Pcap to capture and feed your input makes replaying sessions very convenient, as long as they don't need any interactivity.