From: Dan Tang <firstname.lastname@example.org>
To: email@example.com <firstname.lastname@example.org>
Date: Wednesday, 19 May 1999 11:11
Subject: Re: [Emerald] IP
>From: Duane Schaub <email@example.com>
>To: firstname.lastname@example.org <email@example.com>
>Date: Tuesday, May 18, 1999 11:16 PM
>Subject: Re: [Emerald] IP
>>I think that you could build an asp page that looks at the users IP... If
>>the user is local, then check the account that they are logged in on.
>Not practical, most user would simple enable the proxy on every thing, even
>the ISP's internal network, so you web server could not konw where the
>requester come from except proxy server. Unless you would configure each
>cilent's browser properly through configuration server, but take too much
>effort to maintain it.
>>the account is inside of the grace period... ie, after the expire date,
>>before expire plus extension, or some variation, then redirect to the
>>I don't have one built, but it would be concievable to build this into the
>I built one, it worked OK, but as soon as proxy is enabled, no go.
>> Unfortunately, you don't get users who don't use your home
>>page. An alternative would be something like an ICQ watch program. On
>>connection, it would connect to a web page on your server and get the
>>account status and any "sysop" or system messages that could be posted
>>a special email account for user notifications. It could be developed
>>a very full-featured module that could be installed automatically by the
>>IEAK.... Hint, Hint... Some enterprising programmer might look at this.
>>There are a number of Wrapper programs out there already for IE and
>>netscape. I would not be very difficult to get one of these to provide
>>this functionality. You could also use the Channel protocol to push
>>newsletters or customer web pages to the customer.