Re: Restore Sessions vs. Manage Reports on Server

On Thu, Nov 04, 2004 at 03:38:40PM +0100, Renaud Deraison wrote:
> That being said, I'm considering getting rid of session saving
> altogether. Not many people use them, it's an under-tested feature,
> session restoration is quite slow, and I'd like to simplify the source
> code of nessusd as much as possible. 
> 
> So I'd advise you to leave that part alone for the moment. At worse,
> I'll re-implement it "correctly" in the future, but at this time it
> just gets in the way.

OK, so I could make it just a "Manage Reports on Server" feature in the GTK
GUI. That means

1. to have a special dialog to do this management
   (2 actions: Import or Delete a Report).
   This is essentially the corresponding list widget and buttons of the
   current target page.
2. Move the configure option "store session on server" of the target
   page to the page "general" as "store reports on server".
3. The option "store empty session" of the target page could be disable
   for the GUI as it makes no real sense in this context.

This proposal is actually another view on the session-saving feature for
the user. This view is a more narrow one than what the session-saving
is actually able to do and it basically says: you can store your reports
on the server and retrieve them from different clients.

Eventually, once you decided how to proceed with the session saving
feature it is possible to change the view again and reactivate some
GUI code.

Is this a reasonable approach?
(quick response would be appreciated, we are trying to have Nessus
GTK Client feature-complete by the end of this week).

All the best

	Jan
-- 
Jan-Oliver Wagner               http://intevation.de/~jan/

Intevation GmbH                      http://intevation.de/
FreeGIS                                http://freegis.org/
_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel