At 11:29 am +0000 28/11/01, John Morrison wrote:
>(comment inline:)
[snip]
>> This snippet raises two issues (to me anyway):
>>
>> 1. it introduces the concept of a "WritableSource", ie. a
>> Source that can
>> be read from and written to.
>> obvious candidates are the pseudo protocols:
>> context://, file://, xmldb://.
>> Should include the ability to temporarily "lock" the Source.
>>
>> we currently rely on ad hoc solutions for this, we
>> have no general way of
>> modifying existing content, unless it is stored in SQL
>> not everyone wants to work in SQL (as the
>> popularity of FP showed us)
>
>Could we use a version control software (CVS/VSS...)?
yes, if:
a. this idea or something similar (to the WritableSource) is taken up
and
b. someone implements cvs as a pseudo protocol, ie.
cvs://server/repository/ etc etc.
I am (for my sins) having to use a (very very very nasty) CMS at the moment
(for a client), Roxen Platform (jeez what a mess!) but it has a built-in
CVS which is a very useful bit of functionality for a CMS to have IMHO.
[snip]
Thanks for the response
regards Jeremy
--
___________________________________________________________________
Jeremy Quinn Karma Divers
webSpace Design
HyperMedia Research Centre
<mailto:[EMAIL PROTECTED]> <http://www.media.demon.co.uk>
<phone:+44.[0].20.7737.6831> <pager:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
