I'm supporting this kind of flexibility.
The reasons:
1. I worked for a company and wrote proprietary dissectors
and public ones. So reality is that there are proprietary
ones. And I think it helped Ethereal that I could integrate
them pretty nicely, because other found the tool quite useful
and made some stuff public and supported work on public stuff.
So in the end it helped.
2. If you really want to do it, people will just do it and patch
the system more.
3. I like this kind of flexibility. Possibly we can also use it
in the public. Maybe there is a website describing a protocol
better than the page in the Wiki and no one wants to do that
work on the Wiki.
Best regards
Michael
On Aug 31, 2005, at 17:31 Uhr, Joerg Mayer wrote:
On Wed, Aug 31, 2005 at 02:40:14PM +0200, Thomas Boehne wrote:
On Wednesday 31 August 2005 14:00, Jaap Keuter wrote:
With the risk of getting flamed I want to float this idea. Currently
Ethereal can 'leak' information to the world by refering back to the
Wiki as online protocol reference.
I patched my gtk/main.c to redirect accesses for my own plugins to our
local Wiki, which works quite well. However, it would be nicer if
there was an API to set the URL from the plugin code (thus allowing
each plugin to have it's own URL). So instead of adding a boolean
field hfinfo->proprietary I would add a pointer to a URL (which should
default to wiki.ethereal.com, if unset).
I'm stronly against either solution.
a) I'm no fan of proprietary stuff and if people really feel like using
them then they should patch their version of ethereal - either we
put the dissector into ethereal - that's fine, or we don't. But I
see
no reason *at all* to fix problems that may only occur if people use
proprietary dissectors.
b) Making the URL configurable we forster private clones of the wiki
that
will quite likely be "enhanced" even on "public" dissectors.
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.
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
