It is taken care of in version 0.0.2, and the problem wasn't about how to detect if the server was available, it was how to deal with how node handles http requests as asynchronous and doesn't provide a reasonable way to use them in otherwise synchronous code.
In the end I ended up using synchronous requests that are depreciated and may not work in the future. The only other real solution is to redo the checks in the core for which savers are available. The problem about not knowing if a saver is available if it isn't ready when the wiki is loaded is a core problem, it isn't something I can fix without modifying the core. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d5438198-55f2-4341-b128-8c41584c5857%40googlegroups.com.
