Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] HTTP object export

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Stephen Fisher <stephentfisher@xxxxxxxxx>
Date: Thu, 1 Mar 2007 17:06:20 -0800

On Wed, Feb 21, 2007 at 11:10:51PM +0100, Sake Blok wrote:
> On Wed, Feb 21, 2007 at 09:24:45PM +0100, Ulf Lamping wrote:
> > 
> > Sake Blok wrote:
> > >
> > > Would't this be option be feeling more at home under the "File" menu?
> > > It is about exporting parts of the data-stream. My suggestion would be:
> > > "File | Export | Objects".
> > 
> > Yes, you're right, File is the place to go. "File / Export / HTTP 
> > Objects" might be ok.
>
> Maybe "File | Export | Objects | <protocol>" would be more scalable
> (although initially it would mean an additional click).

The File -> Export menu is currently greyed out (disabled) when there is 
no capture file open (which also means it is disabled when running a 
live capture).  The export objects feature can run while a capture is 
going and will update the window in real-time.  Is there any harm in 
stopping the disablement and exposing the other features in the Export 
menu long as we have a capture file open -or- are running a capture?


Steve

  • Prev by Date: Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
  • Next by Date: Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
  • Previous by thread: Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
  • Next by thread: [Wireshark-dev] User information in the packet
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation