Thinking of Wiki as a source of information, it has the
restriction that this information can be added
only by
humans for the time being.
I think, there should be a possibility for scripts/programs/automatic
processes in general to add information to a Wiki topic (including
proper
RCS and ChangedBy handling).
--
DanielKabs - 22 Feb 2001
One of the features on my TODO lists is an email interface. Of course my TODO list isn't been complete that fast at present. Something like this would require some autherication work as well.
Note it is possible to just write some LWP perl scripts to do what you want.
--
NicholasLee - 22 Feb 2001
Regarding authentication, one way to go is an ALLOWTOPICCHANGEBYSCRIPT or SCRIPTACCESS variable that could be set to enable access to a certain topic or page for automated editing. Further authentication
could be dropped then.
And what about providing a
general interface for automated access, which could be used for email access as well?
Btw, what is a
LWP perl script?
--
DanielKabs - 23 Feb 2001
LWP = Lib Web Perl.
See
http://www.linpro.no/lwp/
--
MartinCleaver - 23 Feb 2001
Why add variables to handle script authentication? Seems no need to to overly complicate things.
Just get the script to use std HTTP auth if its done by LWP.
--
NicholasLee - 23 Feb 2001
I understand that an external script can handle authentication.
Nevertheless I think TWiki should provide a different means of
access for scripts than "edit", e.g. a special cgi-program with
an ADD or OVERWRITE mode would reduce the costs for programming an
external script.
--
DanielKabs - 01 Mar 2001
This is exactly what
WebServices is about.
--
MartinCleaver - 11 Jun 2001