[Guy Harris <guy@xxxxxxxxxx>]

> > > I don't follow, this is what we do today. The child dissector sets
> > > the conversation dissector if it is needed. Are you saying that we
> > > replace this with a system that creates a conversation for anything
> > > that uses dissector_try_port?
> > 
> > Yes.
> 
> Why?

Is there any reason for a conversation *NOT* to be created on a port
match, given that there's the risk of "split dissection" if the client
port happens to be one for a protocol that Ethereal dissects?

If not, then having it done for the dissector by "dissector_try_port()"
would be more convenient than obliging all dissectors to do it
themselves.