I am answering the last questions from the previous MultiUser thread here to move to a shorter thread for people using this in the browser and because they are relevant here. So please put new replies in this thread instead.
Ed, 1) I have added more default mime-types so as long as I didn't miss any that you want to use you won't have to edit it. But if you do make a mimeMap in the settings it takes precedence over the default version. Unfortunately at the moment removing objects from the settings json isn't quite as straight forward as removing single field properties. To remove your custom mime-map first either rename or delete the tiddler $:/WikiSettings/split/mimeMap and then in the settings in the $:/ControlPanel it should show "mimeMap": "$:/WikiSettings/split/mimeMap" and if you click on the value $:/WikiSettings/split/mimeMap it should let you delete it like a normal field. 2) The "suppressBrowser": "" line is a property that doesn't have a value. If this is set to true than the browser won't open automatically when you start up the single executable version of Bob. Having extra or unused properties in the settings doesn't cause any problems other than possibly visual clutter. 3) I am glad it works well! I am not sure if much of the praise for it working on old hardware should go to me, that sounds like praise for Jeremy and the tiddlywiki devs who have worked on making it efficient. 4) I have no idea how many people could simultaneously edit a wiki at the same time, I haven't had a chance to have more than 3 active people on the same wiki at one time. I did a test where I had 10 or 15 browser windows open at the same time and they all had their own connection without any trouble, but that isn't the same as simultaneous editors. To my knowledge there is no built-in limit to the number of simultaneous connections the server can support so the limit would probably come from hardware or communication limitations. This may be a much longer answer than you were hoping for. I hope that it could easily support 36 people, each new connection adds almost no overhead on the server. I expect that the biggest problem would be people getting in each others way if they are all trying to edit simultaneously. Another problems is tiddler naming, the only mechanism for preventing overwrites of tiddlers is that the edit button is disabled. If you have 10 people who try to create a tiddler with the same name (like New Tiddler), each one will overwrite the previous persons edits. There isn't a lot of communication required between the server and the browser. There is the initial page load over http(s) which may be slow for people if you have everyone trying to load it at the same time. That shouldn't kill the server, just slow it down. When editing a tiddler normally (clicking on the edit button or new tiddler button) there is only one message sent when the tiddler is saved. I have been able to import single file wikis that have hundreds of tiddlers into a Bob wiki without any trouble and for that each tiddler gets its own message sent. That is from one connection instead of having a hundred different messages on a hundred connections, I don't know if that would make a difference. I have not had a wiki crash because of too many simultaneous edits but it may be possible. I think that a more likely result is losing edits, someone may create a tiddler that doesn't get saved by the server if there are too many tiddlers being created at one time. I haven't seen this happen yet, but I think that is the most likely problem. Tony, Let me know if you run into any problems! -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5325abac-2ad2-4f55-a624-98e7f9a308da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
