469,643 Members | 2,061 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,643 developers. It's quick & easy.

.NET Alerts Compliance Criteria Confusion

Hi, I posted this in the GotDotNet .NET Alerts forum, but that was 3 days
ago and still no reply so I'll try my luck here. My apologies if there's a
better group to post this question in, but at last check there was no Alerts

I've been reading through oodles of the SGK documentation for the .NET
Alerts SDK 5.02, and something struck me in the Compliance Criteria section:

"6. All of your pages work on Netscape version 4.7 or later and Microsoft
Internet Explorer version 4.0 or later."

What is the scope of "All of your pages..."? Is it simply all of the
mandatory .NET Alerts pages (signup, change preferences, etc.), or is it
literally *all* of the pages on the website?

Question number 2: We were hoping that when starting off with the Alerts
that we could start off with some "private" alerts, and then gradually phase
in public alerts. By "private alerts", I mean alerts only available to
people within our company. For example, create an alert that notifies me
whenever a client register's a domain name from our web app. Is this
creation of a "private alert" possible given the compliance criteria and the
Mandatory Page Requirements? Can we gradually phase in public alerts? Or do
we have to create a set of public alerts first before we do anything?

I hope that makes sense... please, fire me any questions for clarification
that you might have.

Thanks in advance.

- ryan.
Jul 21 '05 #1
0 1298

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by rhompi | last post: by
100 posts views Thread by Roose | last post: by
reply views Thread by ryan baldwin | last post: by
26 posts views Thread by wardy | last post: by
4 posts views Thread by nick | last post: by
34 posts views Thread by aljamala | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.