mathieu's questions

Is it possible to send an email alert when a field of a list is empty ?

I've tried the following :

• Create a custom list, add a field named "TestField"
• Create a personal view named "TestView", filter : Show when column "TestField" is equal to "" (leave the box empty)
• Create an alert, immediate email when items appearing in "TestView" are modified
• Create an item with both fields filled
• Create an item with only title filled

Now you should receive two alert emails, but in the view "TestView" there is only one item. Is it a bug ?

Clarification : even though the item with "TestField" filled doesn't appear in the view (filtered on "TestField" empty), an alert email is sent. The alert is related to "TestView", so it shouldn't be sent, as "TestField" is not empty.

Currently when we want to access an internal site from Internet (IIS with NTLM auth), we have two login screens that appear :

• step1 : LDAPAuth, from the BlueCoat that check login/password validity against Active Directory
• step2 : NTLM auth, from our application.

Is it possible to configure the reverse proxy to use the LDAP credentials provided at step1, and give them to whatever application that requests them ? Of course, if those credentials aren't valid, nothing happens.

We're using BlueCoat SG400.

Update : we're not looking for SSO where the user doesn't have to enter a password. We want the user to enter his domain credentials in the LDAPAuth dialog box, and the proxy to reuse it to authenticate against our application. Or any application that uses NTLM. We've only got 1 AD domain behind the reverse proxy.

Suppose you have this fancy new site, with lots of data (like big images), and you're about to put it online. If you do "too much" publicity, during the first days, the site will be overwhelmed with requests.

How can I mitigate this risk ?

I've thought of

• going live gradually, like SO and SF : "private" beta, public beta, public
• allow X connections sessions concurrently, so the connected user still have good experience of the site, and the others have a nice apology message

I can't :

• buy more servers, as after the first days, the site will have a lot less traffic :)

What kind of optimization (performance or whatever) do you use when going live with IIS (on windows 2003) ?

Currently, I use 1 application pool per web site, but I think I can do more :)