Re: Force refresh on Netserver Shared Folder on Windows -- MIDRANGE-L

Subject: Re: Force refresh on Netserver Shared Folder on Windows
From: Bradley Stone <bvstone@xxxxxxxxx>
Date: Mon, 20 Mar 2017 11:44:03 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Mon, Mar 20, 2017 at 10:27 AM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

Yeah, would be cool to use that exit point and then queue up the work in a
data queue or message queueing sub-system like Websphere MQ, Rabbit MQ or
Micsrosoft MQ.

Then he could eliminate the bottleneck by scaling up the process as it
slows down without running into file processing collisions or slowing down
throughput.

Fire up a couple VMs and have them monitor the queues and processing
becomes infinitely scalable.

Maybe... but I doubt my customers would want to pay licensing for that many
VMs... its high enough for one PC. ;)

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Force refresh on Netserver Shared Folder on Windows , Bradley Stone

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.