<div>Well, you could make a mail recipient that belongs to your web service. Then use the existing email notification to cc your service, with appropriate keywords in subject line, then use the "you have mail" event to trigger parsing the keyword and matching against a current user connection.
</div>
<div> </div>
<div>It could be pretty klugy, but OTOH there is a guy somewhere in the universe who uses your same IIS/ASP/Whatever setup and who would do that in one line of perl. Not me though.</div>
<div>Peter<br><br> </div>
<div><span class="gmail_quote">On 10/16/07, <b class="gmail_sendername">Sean Ward</b> <<a href="mailto:SeanWard@msn.com">SeanWard@msn.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I've started work on a web service which contains several potentially<br>long running processing steps (molecular dynamics), which are perfect to
<br>farm out to the fairly large (90 node) Beowulf I have access to. The<br>primary issue is translating requests from the event driven web service,<br>to job queues, and back again upon completion. Specifically, the major
<br>queuing systems I have immediate access to (Sun Grid Engine and Condor)<br>only support e-mail based notification of job completion. Starting jobs<br>isn't an issue, as my service can simply ssh over and execute shell
<br>scripts as needed to start things up, the problem is reliably being<br>informed when the jobs fail or complete, via any programmatic method<br>(such as executing a shell script, calling a web service via SOAP/etc,<br>
or an asynchronous message library). My other problem, ensuring that<br>these web service requests don't starve in house jobs on the Beowulf is<br>easily handled via the priority levels built into all the various job<br>
managers, although being able to checkpoint a long running job would be<br>a plus (such as is supported by Condor).<br><br>I am currently investigating modifications to either Condor (more<br>complex to update, but checkpoint is useful) or Ruby Queue (very easy to
<br>update for reliable notification) to solve this issue, but wanted to be<br>sure I wasn't overlooking any existing solutions to programmatic based<br>queuing and receiving notifications on jobs in a Beowulf environment...
<br><br>-Sean<br>_______________________________________________<br>Beowulf mailing list, <a href="mailto:Beowulf@beowulf.org">Beowulf@beowulf.org</a><br>To change your subscription (digest mode or unsubscribe) visit <a href="http://www.beowulf.org/mailman/listinfo/beowulf">
http://www.beowulf.org/mailman/listinfo/beowulf</a><br></blockquote></div><br>
!DSPAM:471656f5239911446633523!