Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Execute a outproc com server on remote machine
Message
From
16/01/2013 16:29:45
 
 
To
16/01/2013 16:06:39
Joel Leach
Memorial Business Systems, Inc.
Tennessee, United States
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2008 Server
Miscellaneous
Thread ID:
01562467
Message ID:
01563038
Views:
41
Hi Joel.

First, I would like to tell you how much i like your ParalleFox. It has made my FUnit Test Case Suite utility perform far faster, then it did executing each test in sequence.

I have forgotten about COM+. I will investigate it.

The whole idea of passing task to other machine is only in my head at the moment. Just doing some checking. The PF code does not seem to prevent it. So I am just looking.

>ParallelFox works only on the local machine. There are a multitude of methods for passing requests to a server, but besides DCOM, I would also take a look at COM+. Craig Berntson wrote some articles on the subject.
>
>>Actually, it is ParallelFox that I am implementing into my Test Case ( FUnit ) utility. So far it is working great. I am investigating what it would take is pass tasks to other available machines.
>>
>>>He Greg,
>>>
>>>I had a project like that many years ago -- when security wasn't what it is today. It involved processing ACH transfers, which could pile up if a server went down, or if the flow was more than the existing servers could handle. I got it working, but it was cumbersome, and so I re-designed it to a) have one server be a listener; b) if a machine observed there was no listener, it became the listener; c) the listener assigned tasks to all machines that had registered as servers; d) if a task was assigned to a worker machine but went over a time limit, the Listener re-assigned the task to an open Worker. Thus, machines could be taken offline or added as needed (we didn't go so far as to fire up machines).
>>>
>>>It all ran off data, as you probably surmised by now. Worked fast and great.
>>>
>>>The client didn't like it because it wasn't DCOM. Oh well.
>>>
>>>Today you would build it with queues, but I'm not at all certain that having it run the way I did 11 years ago wouldn't be the more robust solution, nor do I think queues would be faster.
>>>
>>>The one thing I would do if designing it today, which was irrelevant back then, is use ParallelFox to utilize all the cores on a given machine. Each Worker would have an exe that ran multiple tasks in Parallel. The exe would, on completion of a task, mark it finished in the workflow table, and grab another to be run by the now empty process. PFox is ridiculously easy to use, fwiw. Great job by Joel.
>>>
>>>Hank
>>>
>>>
>>>
>>>>Hi All.
>>>>
>>>>In part of a recent project, I would like to call a remote outproc server (EXE) on a different machine. Therefore, off loading local task to other machines.
>>>>
>>>>Is DCOM still used? If not, what has replaced it?
Greg Reichert
Previous
Reply
Map
View

Click here to load this message in the networking platform