Geeks With Blogs


View Anthony Trudeau's profile on LinkedIn

Add to Technorati Favorites

Anthony Trudeau

Initialization parameters allow you to initialize the state of an event control based on your environment.  For example, you might have a connection string defined as a initialization parameter, so that the connection can easily be changed.  Registration arguments are conditions you place on the link between a producer and consumer.  The condition determines whether or not an appropriate event is passed to the consumer.

Initialization parameters and registration arguments are defined within the Event Workflow Editor and can be changed only at design-time.  This may be too restrictive.  What if you have a need to change the state on an object tied to the argument, and have that change persist?

Here's an example.  I'm creating scheduling event controls that will provide interval and calendar based functionality.  There is no issue with the interval schedules.  However, calendar based schedules shouldn't be able to run multiple times.  It could be problematic to have a daily scheduled event run twice on a day, because the Edge Process Manager (EPM) was restarted for some reason.

As you can see this example highlights the need to persist at least the last run date/time for the scheduled event.  But, there is no provision for this need in the iMotion Edgeware.  So what can be done?  Luckily, there is no restriction to the content of an initialization parameter or a registration argument.

Read the full article

Posted on Tuesday, May 2, 2006 4:01 PM .NET | Back to top

Comments on this post: Changing initialization parameters and registration arguments at run-time

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Anthony Trudeau | Powered by: