Then again one could assume if a record existed for that region even if it were offline, that it's spot is reserved.<br><br><div class="gmail_quote">On Mon, Feb 2, 2009 at 8:50 PM, Frank Nichols <span dir="ltr"><<a href="mailto:frank@thenichols.net">frank@thenichols.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">To me the region does not need to know if or when the reserved status<br>
would expire. Some process/module must have set it to reserved, and to<br>
me would then assume the responsibility of knowing when/if to expire the<br>
reservation.<br>
<div class="Ih2E3d"><br>
Dahlia Trimble wrote:<br>
> I would think if a "RESERVED" state were added there would probably<br>
> need to be an expiration date associated with it.<br>
><br>
> On Sat, Jan 31, 2009 at 8:23 PM, Frank Nichols <<a href="mailto:frank@thenichols.net">frank@thenichols.net</a><br>
</div><div class="Ih2E3d">> <mailto:<a href="mailto:frank@thenichols.net">frank@thenichols.net</a>>> wrote:<br>
><br>
> There is a member in RegionProfileData (regionOnline) which is<br>
> currently<br>
> not used and does not exist in the region db table. I would like<br>
> to add<br>
> it to the region table as an enum and not a boolean. Currently the<br>
> code<br>
> assumes a region that has an entry in the region table is online<br>
> (as far<br>
> as I have figured out...) With this field in place we can<br>
> impliment the<br>
> requested feature of reserving regions as well as having regions<br>
> online<br>
> but not available for logins. I suggest the following enums:<br>
><br>
> RESERVED<br>
> OFFLINE<br>
> ONLINE<br>
><br>
> at least for starters.<br>
><br>
> Before submitting a patch to support this, i wanted to get some<br>
> direction and comments from the core developers and architects.<br>
><br>
> Frank<br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
</div>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a> <mailto:<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>><br>
<div class="Ih2E3d">> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="Wj3C7c">><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
><br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br>