Some time ago, Syed.Alam wrote...
>What happened to COM load balancing/middle-tier scalability concepts that
>started with COM Router/Application Center? How do we achieve that
>load-balancing act in .Net framework?
Since .NET uses COM+ for its enterprise services implementation, you should
still
One of the early versions of the FMExpense demo used Isolated Storage in
conjunction with a (slightly modified) local copy of the FMExpense web site
installed to the "MyWeb" virtual client site. This enabled the app to run
locally when disconnected, and sync up with the real site once the user
bec
You can certainly still use Component Load Balancing (CLB) in
Application Center Server to balance DCOM requests.
However, a simpler and (in my experience) more reliable approach is to
use Network Load Balancing (NLB) to balance .NET remoting calls to
server-activated objects. This will work wit
Building management cut our power for an unknown reason for about 18 hours.
http://www.saurik.com/net/exemplar/
Note that the output is quite less than perfect for this usage case :).
"a good job" might be stretching it, hehe...
Sincerely,
Jay Freeman (saurik)
[EMAIL PROTECTED]
- Original
We have not uninstalled Clear Case. We are hoping it does not come to
that. Per the replies I am seeing, this may be our only option.
You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.co
Thomas
On most of these issues we could argue the toss all day and get nowhere. But there are
a couple of concrete points I'd like to pick up on. You say:
"Threads mean that a thread scheduler has to check them regularly and has to blow it's
performance
on this."
My understanding is that with
My application dynamically adds UserControls to it's client area. The
UserControls fire events to update the container applications status bar.
As the UserControls are added to the container I do the following to hook
up the event:
Type type = Ctrl.GetType();
EventInfo ei = type.GetEvent("Update
Andy,
I know of NO (!) operating system so far that is made to handle a high
amount of threads running into hundreds. Threads mean that a thread
scheduler has to check them regularly and has to blow it's performance
on this.
I have been involved in a number of high throughput projects (up to
60.
I think the Synchronised OLTP approach is the best - thinking it through .
Performance could be improved by creating input queues for each transaction
and once the transaction is finished applying them in a big batch -. You
could then trigger an event and any other caches could get the data and d
David ,
I actually agree with Thomas - I would use a threadpool. If a library
requires a single threadid use a higher priotity schedule thread to pass the
work information to the threadpool. Threads are not a performance issue
like going to the DB but they do consume resources and large
Furthermore on everything ..
Have you uninstalled Clearcase or searched the registry for entries ?
Ben
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED]]On Behalf Of Sills, Adam
Sent: Monday, 1 July 2002 9:56 PM
To: [EMAIL PROTECTED]
Subje
Updating caches within the business tier across multiple machines is an
issue I'm currently wrestling with as well!
So far it's been suggested:
1. That an extended sql proc (dll) + triggers on tables could be used to
push updates from the db server to all the webservers/business object
servers i
12 matches
Mail list logo
