Sure, I didn't mean to ask you to implement all of that. Rather, I just wanted you to keep in mind that it would be really useful for other things, and when you face choices in your development try not to hardwire stuff that would preclude using your module for something other than a hotel room. The Hotel Room node might be one place to look at - maybe instead of everything revolving around that node type you could define a generic "reservable resource" node, of which "hotel room" is a subclass (or what passes for a subclass in Drupal ...). Then anyone could make their own "reservable resource" subclass by adding a CCK field or two, which your module would then be able to handle automatically. That's the sort of thing that would make the module generally useful without increasing your work or having you solve 5 different problems at once.