I see what your saying Mirage. In the future if they made it where the Sim could run a script that would be good. but for now, you can use the method I mentioned. I hope this does push openSim forward. This would be a big step in the right direction.<div>
<br><br><div class="gmail_quote">On Tue, Feb 2, 2010 at 4:08 PM, Master_Mirage <span dir="ltr"><<a href="mailto:mirage123@verizon.net">mirage123@verizon.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
correct! and in the grand thought of this. Not everthing is CORE.. thats the<br>
point and the cool part. CORE Opensimulator is that. it is flexable and<br>
complex. Id bet my last dime on kick ass stuff ppl will make from the core!.<br>
Its made to be that and as complex as it is. It has tobe flexable to matter<br>
at all :)<br>
<div><div></div><div class="h5"><br>
John Mieske wrote:<br>
><br>
> why not add a PHP file that does this all for you ? Example : They click<br>
> a<br>
> button that says Visitor John. It gives them a temp user and PW with full<br>
> instructions to their e-mail. They log in. Now the timer on the PHP can<br>
> delete the temp user and PW after 24 hours. You can even have a php that<br>
> refreshes every hour that checks the database and removes the temp users<br>
> that has no need to be there. Make sure you create a seperate database for<br>
> the time limit so that it wont have to be added to the MAIN SQL database.<br>
> If<br>
> the "extra" SQL databse has the name and user's time stamp ready for<br>
> deletion then it removes it from the MAIN database for the name and PW and<br>
> then goes back to the temp and removes it there too. So two databases with<br>
> name and PW to show which is fake.<br>
><br>
> This can be done in many ways. Just a thought.<br>
><br>
> John Mieske / Sonya Penucca<br>
><br>
> On Tue, Feb 2, 2010 at 10:49 AM, Paul Fishwick<br>
> <<a href="mailto:fishwick@cise.ufl.edu">fishwick@cise.ufl.edu</a>>wrote:<br>
><br>
>> I would like to open up one of our worlds to the general public by<br>
>> allowing people<br>
>> to log in as visitors. This is related to the "anonymous login" and has<br>
>> been discussed<br>
>> in various forms, but here is the concept - not sure if anything exists<br>
>> yet in trunk to<br>
>> support this:<br>
>><br>
>> 1. A user logs in using whatever name they want. If authentication is<br>
>> turned off, this is<br>
>> no problem. However, what would be ideal is that when the user logs<br>
>> off, any trace<br>
>> of them is removed from the database-- they do not persist.<br>
>><br>
>> 2. When the user logs in, they have access to the Library part of the<br>
>> inventory, but are<br>
>> unable to load any assets to the server, thus they would have<br>
>> nothing under "My Inventory"<br>
>> or be able to copy items from the Library or the world into My<br>
>> Inventory. The Library<br>
>> would contain all necessities (clothing, basic objects and scripts<br>
>> that they require<br>
>> in the space).<br>
>><br>
>> 3. The user cannot build on the island but can run scripts and navigate<br>
>> performing full<br>
>> interaction.<br>
>><br>
>> #1 is not a huge issue since I would imagine that the incremental space<br>
>> allocation for<br>
>> users just means additional rows in the user/agent tables -- shouldn't<br>
>> take up too much<br>
>> room. #2 is a bigger problem - visitors should not be taxing the asset<br>
>> server. #3<br>
>> can be handled by unchecking both boxes next to Create Objects in About<br>
>> Land->Options.<br>
>><br>
>> Are either #1 or #2 possible? They would seem to be a prerequisite for<br>
>> something approaching<br>
>> basic web page services: people come in, visit, and exit while leaving a<br>
>> minimal trace.<br>
>> Builders on the other hand, have special login names that give them the<br>
>> capability to build<br>
>> and load assets (possible with groups?).<br>
>><br>
>> -p<br>
>><br>
>> --<br>
>> Paul Fishwick, PhD<br>
>> Professor<br>
>> University of Florida<br>
>> CISE Department, CSE 301<br>
>> Gainesville, FL 32611<br>
>> Email: <a href="mailto:fishwick@cise.ufl.edu">fishwick@cise.ufl.edu</a><br>
>> Web: <a href="http://www.cise.ufl.edu/~fishwick" target="_blank">http://www.cise.ufl.edu/~fishwick</a><br>
>><br>
>> _______________________________________________<br>
>> Opensim-users mailing list<br>
>> <a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a><br>
>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
>><br>
><br>
> _______________________________________________<br>
> Opensim-users mailing list<br>
> <a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a><br>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
><br>
><br>
<br>
</div></div><font color="#888888">--<br>
View this message in context: <a href="http://n2.nabble.com/the-concept-of-visitor-tp4501558p4503667.html" target="_blank">http://n2.nabble.com/the-concept-of-visitor-tp4501558p4503667.html</a><br>
</font><div class="im">Sent from the opensim-users mailing list archive at Nabble.com.<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Opensim-users mailing list<br>
<a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>John Mieske / Sonya Pencuca<br><a href="http://johnmieske.org">http://johnmieske.org</a><br>Space Grid Station<br>"Religion - The art of killing people to prove who's imaginary friend is better."<br>
</div>