Re: FN-FORUM Charging for Object Oriented Code

date posted 7th April 2001 20:17

well im not too familiar with php, but with asp you shouldnt have a problem
stopping them reusing your components.

if they're hosted on your server and want to move to another host then
explain to them that your using some of your own components and if they want
to move hosting it will require the asp code being modified or the new host
purchasing the component from you. if they're not going to be hosted on
your server then avoid using custom COM objects - ive pointed out before
that any hosting company that installs dll's willy-nilly should be avoided
at all costs - the first rule of NT servers is: does it work? is it secure?
if both are yes then leave it alone, no service packs or untrusted dll's
unless absolutely necessary or else dont be overly surprised if your server
grinds to an undignified halt at some point in the near future! :)

as for costing, imho you shouldnt charge the client for them unless they
specifically ask for one - in your example of a shopping basket you shouldnt
need a custom COM object for that - and if you find you need one then its
probable you'll need it in the future so it benefits you as well as your
client.

hth

dave ecky

----- Original Message -----
From: "Antonio Gould" [EMAIL REMOVED]
To: "Freelancers Forum (E-mail)" [EMAIL REMOVED]
Sent: Saturday, April 07, 2001 11:19 AM
Subject: FN-FORUM Charging for Object Oriented Code


> Hi all,
>
> Does anyone here use object oriented code for writing web applications (In
> php or asp preferably)?
>
> How do you cost the creation of these objects? For instance, if you
create
> a generic shopping basket which will work on any site, how do you charge
> for this? Do you charge the first client who requests it for the
creation
> of the object, or do you charge each client you use it for the amount it
> cost you to build it?
>
> Also, do you make an issue of them being able to use it in the future?
(If
> it's in php you can't really stop this as far as I know as you can't
> protect the source code - there's no equivalent of making a DLL like you
> can on a Windows system)
>
> Any info would be really handy.
>
> Thanks,
>
> Antonio
>