Thanks for the question.
We are doing some work on this front. At present, it's not quite far enough along to say with certainty that you'll see it in an upcoming release, but here's some thoughts on how it might work:
We're building an extensibility interface that will allow PingPlotter to interface with a variety of plug-ins. Our "prototype" plug-in is a database logging plugin, which creates a unique "session" in the database when you start tracing, and then logs data in the context of that session and hosts.
The basic database structure for our "prototype" looks like this:
Table: Session, Fields: ID, Target IP, Target Address, Target Description)
Table: Sample: Fields: ID, SessionID, DateTime
Table: Host. Fields: ID, SessionID, Name, IP
Table: Response. Fields: SampleID, HostID, Hop, Latency
Table: Route: ID, StartSampleID, EndSampleID
Table: RouteHosts: RouteID, Seq, HostID
As each sample is complete, the data is logged to the database. Route changes and all sessions are automatically logged to the database.
This is all we've done work on so far. We don't have anything done with reloading this data in PingPlotter - we're only writing data. This is really in the form of an example plug-in, and all database variables are hard-coded into the script. We've not written any reporting facilities or any way to access this data - maybe we will before we release it. We've not had many requests for this type of thing yet, but it's interesting territory.
It's a long way from being done, and it's in a development build that has numerous "challenges" that make it impossible to release right now.
Maybe this is more data than you ever cared about <img src="/forums/images/graemlins/smile.gif" alt="" />. This gives you a rough idea of where we're going, but we're not sure where it will end up.
Feel free to comment on / question what we're doing here.