On Fri, May 11, 2018, 4:05 AM Mat <[email protected]> wrote: > Arlen - your categories make much sense but to really clarify: > > Would you say that "services" are really the same thing as "hosting > services"? >
A service is managed by someone else and presents an interface to the end user which requires little to no configuration on the user's part. Storage depends on the service. Tiddlyspot and tiddlyspace stored files on their own servers, whereas twcloud (aka TWitS) and noteself store the data in user-defined locations. > I.e when you say that "services ... manage the data storage internally" > ...is it fair to interpret this to mean that "services" is *someone else* > deciding how you access and manipulate your data (behind the TW UI)? > Whereas in "servers" you have more direct control over how you access and > manipulate your data? Or does "manage the data storage internally" imply > something else? (I think it is the term "internally" that I find unclear.) > A "server" allows you to host your own "service". Maybe that makes it a little clearer. A "service" dictates what happens with your data. For instance, TiddlyServer provides the service of serving and editing files and datafolders side by side. There are practical limitations in the implementation that restrict where the data can be stored (it must be on the filesystem). But the user gets to decide how to work around that limitation (such as serving a folder that is synced with Dropbox). In this case, the server and service are bolted together like an engine and transmission. The twcloud service "restricts" the data to files stored in a users dropbox. But anyone can grab the files off github, modify two strings, and host them on their own server. This service is more flexible since it does not store state on the server and therefore is more like a portable pump that you put in your pickup truck bed and take wherever you need it. The same concept applies to store.php. A "notebook manager" is a desktop application that provides a service. Again, the application and service are bolted together. But with very little modification, I could bolt TiddlyServer onto Electron and make it a "notebook manager". I guess I should have really called them "programs" or "applications". A standard browser is a readonly application when opening file URLs. So we have two types of platforms (aka backends, or "controllers" [in MVC]) -- "servers" (which use browsers for the client) and "applications" (which have the client built in). Both provide services suited to their capabilities. Technically we also have the CLI, but so far that only involves manipulation of the stored data, rather than actually bringing it to the client, so it doesn't really count as a platform. This feels more fleshed out than my first one. > > -- 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/CAJ1vdSTk%3DB%2B63ij%3DqcxF7PndFHwLjZwNdVOZpxufFBr2-wWxfg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
