[tw] Re: tiddlyserver vs nodejs TW5
Thank you both, that's very helpful. Clarifying question: Is it possible to A) have a single "front end" TW5 (whether a single file or multiple - I'm still a little foggy on how this works) that can "look up" a client from all the subdirectories, and load that, save all the changes to that client's info in the subdirectory, then search for the next client's name to load that... or B) would I be required to have each client be a separate self contained TW? the reason being, if I want to make changes in how the front end TW does stuff with the client's content, in the case of A), I'd just have to do it once, but in B) I'd have to change each TW file. Thanks again -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/36b4ab70-2916-40b0-b321-6d76d260d5a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] Re: tiddlyserver vs nodejs TW5
Just so you're clear on the distinction - Tiddlyserver is using the Node server to do what it's doing, along with some clever stuff that Arlen added. So it's a superset. The main advantages are that you can use it with single file wikis and you only need to run one process. On Wednesday, September 20, 2017 at 5:41:57 AM UTC+10, Dave wrote: > > What are the main differences between tiddlyserver and "regular" nodejs > TW5? > > Is one easier to set up (e.g. for computer non-professionals)? > Is one easier to maintain? > Is one better for one type of use vs another use case? > Is one more future-proof than the other? > Is one faster responding during normal use than the other? > > > Here's an example use case: > > Have one master TW5 instance that can switch between folders and access > thousands of different sets of TW data (e.g. customer files), possibly > accessing different clients in different browser tabs, and ideally, being > able to search and analyse data from several clients at once for analysing > data patterns amoung all or certain subgroups. > > > Thanks! > - Dave > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/39ec49f6-9bdf-4d7f-8506-cf8760ca7680%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[tw] Re: tiddlyserver vs nodejs TW5
Hello, My observations (YMMV): 1. Tiddlyserver is easier to set up because you can just drop some files into a folder, configure a file, and go. 2. The maintenance would be if something goes wrong. Probably about the same 3. TiddlyServer can serve up Individual TW's as well as TW's based on separate tiddler files. So it's definitely better if your main concern is single TW files. 4. Node.js is probably slightly more future safe since it's not dependent on a single individual. Somewhat irrelevant since you could always switch. 5. Performance is probably the same, depending more on whether you serve up single TW files or TW's that are based on multiple tiddlers. Only TiddlyServer (TS) can allow you to view external images and pdfs on relative pathways. Only TS can allow you to have multiple tabs, each with a different TW file, all on the same port number. I was not able to use TiddlyServer for shadow tiddler development in a GIT repository. I had to launch from node.js using special syntax. Summary: TS is better for most people in most cases. Node is necessary for certain kinds of github-related development. I'm not sure I understand the details of your use case. Good luck, Mark On Tuesday, September 19, 2017 at 12:41:57 PM UTC-7, Dave wrote: > > What are the main differences between tiddlyserver and "regular" nodejs > TW5? > > Is one easier to set up (e.g. for computer non-professionals)? > Is one easier to maintain? > Is one better for one type of use vs another use case? > Is one more future-proof than the other? > Is one faster responding during normal use than the other? > > > Here's an example use case: > > Have one master TW5 instance that can switch between folders and access > thousands of different sets of TW data (e.g. customer files), possibly > accessing different clients in different browser tabs, and ideally, being > able to search and analyse data from several clients at once for analysing > data patterns amoung all or certain subgroups. > > > Thanks! > - Dave > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/3f2de5ae-7467-4b92-8efb-eeb437238e5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
