When we started with SRS last year we were surprised to learn that the
interface was Perl based. We didn't feel like learning Perl so we wrote an
ActiveX control that implements the majority of the latest SRS command set
(this wasn't fun! I didn't even bother with RACE encoding). I've had this
thing kicking around on my machine for almost a year. When I get some free
time I'll slap some documentation together and release it (late August).
Let me know if you need the object sooner.
----- Original Message -----
From: "Giuseppe Simone Aielli" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, July 30, 2001 1:38 PM
Subject: Re: NT Com Component
> Hi Keith,
> indeed you could save all your info to a database and retrieve it later
from
> ASP, using the SRS order# as a key, as I did.
>
> BUT, the problem still remains! For us, ASP developers, there should be a
> bettere way to run (and enjoy the SRS), and perhaps it's time to make an
> opensource project on a COM SRS client, which could be easily implemented
on
> a ASP application, or even a desktop win32 application, why not?
>
> So if someone on the list is planning to make some efforts in this way,
> please feel free to contact me. I am already running two related projects
> (ASPDNS and EasyWhois) on sourceforge; these are two simple tasks, but the
> bigger picture is to have as many components as possible to make it easy
to
> run a business on Internet with Windows.
>
> Thanks for your attention!
>
>
> PS. several months ago I heard of a COM SRS client, but it's not
opensource.
> Also there is a Java client on the sourceforge site, which is opensource.
>
>
> ----- Original Message -----
> From: "Keith Bent" <[EMAIL PROTECTED]>
> To: <>
> Sent: Monday, July 30, 2001 5:34 PM
> Subject: NT Com Component
>
>
> > I am trying to implement open SRS on a NT platform, is there
> > anybody out there that has a Com component developed that can
> > be used easily by ASP developers???. The current CGI/PERL
> > provided by Open SRS is a problem due to the fact that when we
> > try to implement an on-line payment using our current ASP
> > developed platform we lose the CGI session scope and have no
> > way returning back to registration after getting payment.
> >
>
>
