<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br>At a quick glimps it looks as what I just accomplished today. The page that is downloaded keeps pinging back to the server to give it a chance to post back information.<div>Next step is to find out how the server-internals works. It's a bit of a nusence that I probably will have to consider it 'dead' (not running a thread) .. instead of collecting information in arrays, I'll have to write everything into the proper files (open/read/ calculate something/write/close) for every ping ... all before getting to juggle the 'true' problem-complex. </div><div>I wouldn't have got anywhere without some years of application-programming.</div><div><br></div><div>I'll hit the sack / cheers<br><div><div id="SkyDrivePlaceholder"></div><br>> Nibbling away: Carsten's quite correct, re server-side work needing to be done.<br>> <br>> Now I believe an approach based on xmpp might provide a solution;<br>> Googling for XMPP and collaboration finds several interesting &<br>> possibly suitable approaches.<br>> <br>> Especially interesting, IMO, is<br>> http://www.ibm.com/developerworks/xml/tutorials/x-realtimeXMPPtut/section3.html<br>> <br>> AS<br>> <br>> On 2/17/12, Dave Patton <davep@confluence.org> wrote:<br>> > On 2012/02/17 11:51 AM, Arnie Shore wrote:<br>> ><br>> >> BTW, I believe the OP is looking for handling not a random file<br>> >> (hardly that!) but an 'arbitrary' user-selected one.<br>> ><br>> > Arnie is correct - I should have perhaps said 'arbitrary'.<br>> > The point is that the Reviewer can't necessarily anticipate how<br>> > the 'files of interest' will have been 'organized' by the Workers.<br><br></div></div> </div></body>
</html>