Ethereal-dev: Re: [Ethereal-dev] How is HTTP desegmentation supposed to work?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Olivier Biot" <ethereal@xxxxxxxxxx>
Date: Fri, 6 Aug 2004 10:43:41 +0200
>From Ulf Lamping:

| Guy Harris wrote:
|
| If it's a preference setting only because in case of a problem you
| can switch if off, why is the default to off?

I think there is a historic reason for this.

| I was thinking, that this is disabled for performance reasons. If
| it's not significantly the case, I would really vote to enable all
| the desegmentation/reassembly stuff by default.

I would go one step further, and provide a dialog similar to the
"enabled protocols" for controlling reassembly. Maybe we should add a
proto_register_reassemble_preference() method with a signature like
proto_register_bool_preference() in order to access those settings?

| I've often talked to novice Ethereal user's, which didn't know that
| there's TCP segments out there, and of course didn't know about such
| an option to switch it on.

That's correct.

Maybe we should offer a set of profiles "optimize for speed (no
reassembly)" and "optimize for information (reassembly)"?

Best regards,

Olivier