1) My feeling is B should be a service so that it is not dependent on a
logged in user. The ASP activity from A may occur when there is no active
login, correct?
2) A should not "wake up" B, but B should periodically poll the data. By
the nature of your setup there is some latency for the "B" operation,
meaning it is not as immediate as A doing the store. Therefore if the timer
in the service fires every N Insert_Your_Favorite_Time_Units, then things
should be fine.
3) As I think things should be set up, this question is moot.
"Gilbert Tordeur" <GilbertTordeur@discussions.microsoft.comwrote in
message news:9854ECDE-6BC3-4093-99EB-7926F5F7A0CB@microsoft.com...
Quote:
Context : Windows Server 2003, IIS 6, VB 2008
>
My asp.net application A stores data in an SQL 2000 database. My
application
B (on the same server but under a different userid - not ASPNET) reads
these
data, does its job (big load, low priority) and updates the database. A
does
not wait any answer nor acknowledgement from B.
>
Questions :
1) I think B can be a console application, am I right ?
2) How can A wake up B when A has stored data for B in the database ?
3) How can B wait when it has completed a task, until A wakes it up ?
>
Thank you,
Gilbert