There is a big difference. You'd need some server-side script to mediate
the HTTP requests, otherwise all you have is a (read-only) static
document being served on request.
I can't go into more detail here, but that's just how it works (it's got
nothing to do with TiddlyWiki per se).
-- F.
If it's just a shared network drive (i.e. instead of a web server), it
actually does not (i.e. disregard my previous response).
IIRC, some people have reported weird issues with this on Windows. I
don't remember the details, but I think that got resolved - check the
group archives and the community wiki (tiddlywiki.org).
-- F.
The following page explains why that's not possible on a tiddler-level
without a mediating server-side script:
http://tiddlywiki.org/wiki/Server-Side_Implementations
However, it is possible on a document-level using TiddlyLock (also
listed on that page).
> I'll ask another question whilst at it!
> Maybe I should make a new thread about this but lets give it a shot!
Generally speaking, it's indeed better to create a separate thread for
each issue. However, this seems fine here (provided the notes above
suffice).
-- F.