Too many MIME updates on MIME type creation

[axeld]

The registrar sends out tons of B_META_MIME_CHANGED notices when new MIME types are installed - this should be calmed down to an acceptable number, possibly just one.

[diver]

Could this be related to bug #257?

[axeld]

Yes, probably - but since the delay is now much shorter, the problem should be gone if that was it.

[bonefish]

Actually there weren't that many notifications sent. Usually just one "created" notification and a few "updates" (one for each set property). As of hrev25730 we only send the "created" notification in such cases. For the first boot that reduces the number of sent messages from some 320 to 109. There still are a handful of unavoidable duplicates (for the servers that are started before the mimeset script runs), but other than that there really are that many MIME types involved.

[axeld]

I think reducing the number of messages by two thirds is rather nice. But I think we may want to rethink the whole port limitations at one point anyway. For one, they really should use pageable memory to reduce the memory pressure they may currently impose when ports aren't emptied.