Date:         Tue, 14 Dec 1999 17:46:04 -0500
Reply-To:     dward@sashelp.com
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         dward <dward@SASHELP.COM>
Subject:      Re: SAS/IntrNet licensing (was Re: Perl)
Content-Type: text/plain; charset=us-ascii

My job for the second half of this year has involved exactly what Tim is discussing.  I've come up with a replacement for SAS/Intrnet using Base SAS/SCL, and Perl.  The legal implications are a little frightening though... My company hasn't investigated what this will mean to our clients who will be purchasing the software.

The code is simple enough, as Tim mentioned.  I'll probably post as much of it as I can (I'll need to see what is proprietary) soon to SASHelp.com and let you know when it is available.

Our Internet product combines persistent sessions with session management, none of which SAS/Intrnet does.  These were features that were vital to the success of our current product.

One huge problem with custom CGI interfaces to SAS is that, to my knowledge, SAS can't truly act as a server by supporting simultaneous multiple TCP/IP connections.  I'm stuck with one at a time until I can kick off a separate session that is dedicated to only one user.

David Ward
SASHelp.com

> In our case, cost constraints and the fact that we only deploy
> SAS/IntrNet on our intranet has caused us to drop
> our SAS/IntrNet license - we will be replacing it over the next 6
> months with a mix of in-house SCL and Perl code
> as the glue between Web forms and SAS as the back end. I'll be happy
> to share these developments on SAS-L
> as the code matures (and as time permits).
>
> Tim Churches
> Sydney, Australia



--
----------------------------------------
David L. Ward, Senior Software Developer
DZS Software Solutions, Inc.
Bound Brook, NJ
SAS Related: dward@sashelp.com
Work Related: dward@dzs.com
----------------------------------------
--