To me the region does not need to know if or when the reserved status would expire. Some process/module must have set it to reserved, and to me would then assume the responsibility of knowing when/if to expire the reservation.
Dahlia Trimble wrote: > I would think if a "RESERVED" state were added there would probably > need to be an expiration date associated with it. > > On Sat, Jan 31, 2009 at 8:23 PM, Frank Nichols <[email protected] > <mailto:[email protected]>> wrote: > > There is a member in RegionProfileData (regionOnline) which is > currently > not used and does not exist in the region db table. I would like > to add > it to the region table as an enum and not a boolean. Currently the > code > assumes a region that has an entry in the region table is online > (as far > as I have figured out...) With this field in place we can > impliment the > requested feature of reserving regions as well as having regions > online > but not available for logins. I suggest the following enums: > > RESERVED > OFFLINE > ONLINE > > at least for starters. > > Before submitting a patch to support this, i wanted to get some > direction and comments from the core developers and architects. > > Frank > _______________________________________________ > Opensim-dev mailing list > [email protected] <mailto:[email protected]> > https://lists.berlios.de/mailman/listinfo/opensim-dev > > > ------------------------------------------------------------------------ > > _______________________________________________ > Opensim-dev mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/opensim-dev > _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
