Evan Huus
changed
bug 9552
| What |
Removed |
Added |
| Status |
RESOLVED
|
CONFIRMED
|
| Resolution |
FIXED
|
---
|
Comment # 6
on bug 9552
from Evan Huus
(In reply to comment #5)
> PS, What about the suggested color coding for SPX? Make a separate bug for
> that, or does that go elsewhere for consideration?
Oh, sorry, forgot about that. I don't have any particular objection to a new
colouring rule except that the default set of colouring rules is fairly limited
(each colouring rule slows down the UI a little). The current default is to
colour "ipx || spx" together. IP (v4 or v6) doesn't actually have any rule at
all, since it's almost always carrying some other protocol (tcp, udp, etc)
which gets coloured instead. Is the same true for IPX (ie is it common for IPX
to not have any payload)? In which case should the default filter just be "spx"
at the current colour, and IPX becomes white?
I'm trying to strike the right balance between simplicity and effectiveness of
the defaults, but I don't know enough about IPX/SPX usage to be able to make
informed decisions. What do you think is best?
P.S. One alternative is to make an entirely separate profile like we did for
Bluetooth, since it had so many additional filters that it was worth including
them, but too complex to include them in the "default" set. I don't think this
is the case here, unless you have a large set of other IPX/SPX-related filters
you weren't planning on making default.
You are receiving this mail because:
- You are watching all bug changes.