When I say "Delete", I mean that I want all the stuff about that topic to be gone. The reason is I need topic management to see if they are being used or not. If they are not being used for awhile, I expire the topic and kill it. This is what I should do to save resources. Imagine a large number of hedwig users that start new topics, send messages, etc. All these data build up eventually (and I believe there is no eviction mechanism and policy yet). Even though hedwig lets user to keep messages persistently. I don't think it should persist when the user wants it gone.
Since you said it would possibly break some of the guarantees, I would have to look more into it. If my memory is correct, Ben Reed said adding administrative hedwig function to delete a topic should not be too complicated. If it is indeed complicated to achieve the functionality without breaking the guarantees, I will have to wait or build something around. I need to know little bit more about the hedwig hub redistribution and how it works, if it is configurable, etc. Where should I start (i.e., which java package or classes deal with this)? Regard, On Thu, Dec 22, 2011 at 3:40 AM, Ivan Kelly <[email protected]> wrote: > Sorry, this isn't the model which hedwig uses at the moment. Changing > it, apart from being a large amount of work would also break some of > the guarantees which hedwig currently has. For example, if you create > a topic, someone subscribes and then disconnects, messages are > published to the topic, the topic is deleted and created again, > and more messages are published, should the subscriber when he > connects again get all the messages? only those from the second topic > creation? only the first ones, since that was the one he subscribed > to? > > I'm sure there's a lot of other cases similar to this also. > > -Ivan > -- Daniel S. Kim
