Eladesor
|
| Posted: 08/20/2001, 6:30 AM |
|
Hi,
Can anyone suggest a way of protecting the code (and / or templates - ASP)
written by CC ?
i.e. If I developed a site for a customer using CC and allowed them to test
it (they have their own web space), how can I stop them simple downloading /
editing it and using it themselves?
Obviously the ethos of CC is to rapidly develop web sites, however I don't
want to simply give them away after I've spent time developing them to a
customers needs.
Any help appreciated.
Regards
Eladesor.
|
|
|
 |
Stuart Sammels
|
| Posted: 08/20/2001, 8:34 AM |
|
I never put the site on a clients server until they pay me. I put the site
on my server and let them test it from there. Once you upload to their
server they could change the FTP password and not pay you anything. What
could you do?
After they pay you who cares what they do with the code. If they were going
to take the code and use it again for themselves, then why would they have
you build the site in the first place? I find that most of the people I
build sites for are having me build it for them because they just don't know
how to build it, or they just don't have the time.
"Eladesor" <eladesor@NOSPAMbtinternet.com> wrote in message
news:9lr3cn$a7r$1@news.codecharge.com...
> Hi,
>
> Can anyone suggest a way of protecting the code (and / or templates - ASP)
> written by CC ?
> i.e. If I developed a site for a customer using CC and allowed them to
test
> it (they have their own web space), how can I stop them simple downloading
/
> editing it and using it themselves?
> Obviously the ethos of CC is to rapidly develop web sites, however I don't
> want to simply give them away after I've spent time developing them to a
> customers needs.
>
> Any help appreciated.
>
> Regards
> Eladesor.
>
>
|
|
|
|
Don Oldenburg
|
| Posted: 08/20/2001, 1:30 PM |
|
"Stuart Sammels" <highlanddesigns@hotmail.com> wrote in message
news:9lramm$svm$1@news.codecharge.com...
> I never put the site on a clients server until they pay me. I put the
site
> on my server and let them test it from there. Once you upload to their
> server they could change the FTP password and not pay you anything. What
> could you do?
> After they pay you who cares what they do with the code. If they were
going
> to take the code and use it again for themselves, then why would they have
> you build the site in the first place? I find that most of the people I
> build sites for are having me build it for them because they just don't
know
> how to build it, or they just don't have the time.
>
>
I agree totally Stuart.
On a further not-- I will never give a customer the .ccs file. If you've
ever tried to edit the direct code from CC -- they do a pretty good job of
scattering it around. It makes sense to make any changes through CC direct,
and if you have that file under lock and key -- it only improves your
situation. I don't even acknowledge to clients that I'm developing with
this (or any other tool).
Don
>
>
>
>
>
>
> "Eladesor" <eladesor@NOSPAMbtinternet.com> wrote in message
>news:9lr3cn$a7r$1@news.codecharge.com...
> > Hi,
> >
> > Can anyone suggest a way of protecting the code (and / or templates -
ASP)
> > written by CC ?
> > i.e. If I developed a site for a customer using CC and allowed them to
> test
> > it (they have their own web space), how can I stop them simple
downloading
> /
> > editing it and using it themselves?
> > Obviously the ethos of CC is to rapidly develop web sites, however I
don't
> > want to simply give them away after I've spent time developing them to a
> > customers needs.
> >
> > Any help appreciated.
> >
> > Regards
> > Eladesor.
> >
> >
>
>
|
|
|
|
Chip Cotton
|
| Posted: 08/23/2001, 6:26 PM |
|
This is exactly the problem we now face, and I've only found one
solution for it.
We have to realize that people are thinking they can pay the same for
dynamic webs as they did for "word processor" webs.
This was alerted to me when a client candidly remarked that after he
paid me for setting up a client management / order system for his
business, he would then go out and SELL THE CODE TO OTHERS IN HIS
INDUSTRY...
My solution is to EXCLUDE these engagements, and *INSIST* that we work
on an *Application Service Provider* basis, where *I* have *exclusive*
access to the web pages (I give them an FTP directory).
This means that *I'm* in charge of the hosting, etc.
I've found a good web hosting reseller account and I take it from
there.
My alternatives would be to charge 2x for the sourcecode and 3x if
they're thinking about reselling the code....
The "closeout" clause in the contract is that the clients has *full*
rights to all the *graphics* and *DATA* of the website (they can
download the pages and post static copies on their next web, of
course)
This works out simply because if they don't know what they're doing,
they'd want you to manage it anyway, but if they DID know what they're
doing, you'd be giving up your Codecharge "advantage" by letting them
at the pages.
Of course there are those who don't care about making money for their
time...
On Mon, 20 Aug 2001 14:30:00 +0100, "Eladesor"
<eladesor@NOSPAMbtinternet.com> wrote:
>Hi,
>
>Can anyone suggest a way of protecting the code (and / or templates - ASP)
>written by CC ?
>i.e. If I developed a site for a customer using CC and allowed them to test
>it (they have their own web space), how can I stop them simple downloading /
>editing it and using it themselves?
>Obviously the ethos of CC is to rapidly develop web sites, however I don't
>want to simply give them away after I've spent time developing them to a
>customers needs.
>
>Any help appreciated.
>
>Regards
>Eladesor.
>
|
|
|
|
Eladesor
|
| Posted: 08/27/2001, 10:20 AM |
|
Chip,
You hit the nail - right on the head!!
Without an alternative to affording every customer an account with FTP
access, then the developed CC product is (from a developers point of view)
somewhat limited in it's distribution.
Yes it's easy to 'lock' the DB file in a folder away from the client, but as
you will appreciate there are circumstances where developed code must be
viewed or distributed before it's finally agreed upon.
To simply say - who cares once they've paid you - is (no offence intended to
previous posters) is a not the way I wish to conduct my business. Basically
for the same reasons as you outline.
The situation that I am in, is similar that which you mentioned. A new
client has asked for a specific site design - I know that once it is
complete, they can easily transfer it to the other seven members of their
group.
Don Oldenburg posted Quote : to take the code and use it again for
themselves, then why would they have
you build the site in the first place? - no offence Don, but they
might not be able to build the site, but virtually anyone can easily alter
the 'headers' and 'footers', and in the case I refer to, they would have
gained seven sites for the price of one!
sorry for the delay in responding - newserver fault 
Regards
Eladesor.
|
|
|
|
|
