The starting point is to define a message based interface for using epan. I believe the best place for doing that is the wiki with the help of the other developpers.
Then there's the architechture of the system itself.
For which I think we have two or three sub-projects here. I believe more people should come in if we want it done in a summer.
For the server:
My idea is a concurrent server (one that forks as epan cannot run concurrently) that uses websockets.
That needs a c program that uses epan and talks JSON via stdin and stdout. Something similar to tshark, but interactive, that uses JSON encoding.
And a wrapper for it that invokes it and mantains it, running on an http server.
For the client we need an html/_javascript_ application that uses our server.
There should be a _javascript_ library plus a set of labeled html templates, and a program that using them interacts with the server.
\Lego
