The CGI's are not implemented in C, they were written by our excellent PHP
guy, Donny Simonton. The backend code is in C - a daemon process that runs
and scans for modifications to the local database. When these changes are
detected the appropriate commands are sent to OpenSRS.
However I disagree that there are no advantages to C over Perl for CGI's -
if your CGI is going to receive an incredible amount of traffic, ANYTHING is
better than Perl, in terms of speed and system resource usage.
peace
.---------------------------------------------------------------.
| bleachboy bboy at bboy dot net +1 (615) 260-4931 |
| ICQ 1839892 UNIX: Because you want to USE your computer |
`---------------------------------------------------------------'
> -----Original Message-----
> From: alex@dayak.com [mailto:alex@dayak.com]
> Sent: Sunday, April 09, 2000 11:16 PM
> To: bleachboy
> Cc: dev-list@opensrs.org
> Subject: Re: On code-sharing and coding obligations
>
>
> I'm sorry. I thought the days of doing cgi's in C were long
> gone. Ah the
> days when I didn't know Perl and had to churn out cgi code in C.
> There is absolutely 0 advantage to doing a site in C over Perl. In fact,
> unless you are ver, very VERY carefull with your mem allocations and how
> you pass variables your site will be vulnerable to buffer overflow
> attacks.
>
> Good luck!
> Alex
>
> bleachboy writes:
>
> >
> > IMO our website at http://www.directnic.com/ exemplifies this
> philosophy!
> > There's not a bit of Perl on the site. I did the backend
> implementation
> > from scratch in C. Also check out my Linguatron -
> > http://www.directnic.com/cgi-bin/ltsearch.cgi - just shows what
> you can do
> > if you are willing to WORK!
> >
> > peace
> > .---------------------------------------------------------------.
> > | bleachboy bboy at bboy dot net +1 (615) 260-4931 |
> > | ICQ 1839892 UNIX: Because you want to USE your computer |
> > `---------------------------------------------------------------'
> >
> > > -----Original Message-----
> > > From: owner-dev-list@opensrs.org [mailto:owner-dev-list@opensrs.org]On
> > > Behalf Of Grant Kaufmann
> > > Sent: Sunday, April 09, 2000 6:08 AM
> > > To: dev-list@opensrs.org
> > > Subject: On code-sharing and coding obligations
> > >
> > >
> > > The whole OpenSRS model on code-sharing interests me. Many
> people write to
> > > this list asking for code to do certain things, and in many
> cases they are
> > > given the code they want. People regularly make demands on what
> > > the OpenSRS
> > > sample implementation must do, and get edgy if a timeline isn't given.
> > > This strikes me as quite weird. When other SRS systems
> connect you up, you
> > > get a _sample_ implementation and a spec for how the system
> works (and the
> > > perl-code is plenty good for a spec). You are expected to
> write your own
> > > systems to give value-add to your clients.
> > > With the OpenSRS users, it looks like lots of people with little
> > > experience
> > > in domains or programming and just expecting a cheap way to
> > > register domains
> > > and expect the community and OpenSRS to do all the work for them.
> > > If you want a system that offers domain-name alternatives, hire
> > > someone and
> > > write it and offer it as a value-add. IMHO this is the
> > > responsibility of the
> > > reseller, not OpenSRS. I believe the RITE test should be far more
> > > difficult
> > > and OpenSRS should insist that the potential client has the necessary
> > > technical resources to genuinely support their system.
> > >
> > > --
> > > Grant
> > >
> > >
> > >
> > >
> > >
> >
>
>
> Alexey Zilber
> DAYAK
> Need to register or transfer a domain?
> www.dayak.com charges only $15/year.
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:27 EDT