Wireshark · Wireshark-dev: Re: [Wireshark-dev] performing cpu/time intensive computation in aprotocol dissector

["Martin Corraine (mcorrain)" <mcorrain@xxxxxxxxx>]

My vote goes to 1.

-martin 

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Joerg Mayer
Sent: Thursday, August 07, 2008 9:12 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] performing cpu/time intensive computation
in aprotocol dissector

On Thu, Aug 07, 2008 at 01:30:25PM +0200, Sake Blok wrote:
> > You could leave the code in there, and have an 'identify weak keys' 
> > menu option.
> > 
> > But at present I'm changing my vote to 1) Don't include the code at
all.
> 
> All considering, I vote for 1) as well.

I still strongly prefer 2) (optionally identify)

 ciao
     Joerg
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev