3

I read this C# Object Pooling Pattern implementation so my question: does one have to implement own Object Pooling strategy in ASP.NET whereas this exists in Java EE?

Well I'm upset as I prefer .net platform to java, but here in java it's done without being a guru. I'm surprised ASP.NET didn't implement at least the same and even better.

Community
  • 1
  • 1
user310291
  • 36,946
  • 82
  • 271
  • 487

1 Answers1

1

Recently I've learned that .NET covers this for atleast some scenarios.

BufferManager Class

Is an object pool for buffers. I don't see any readily available way to extend this for other purposes short of decompiliation & reverse engineering. However it's possible that a more usable class exists somewhere deep in .NET.

Also in regards to C# Object Pooling Pattern implementation the complexity involved in this will reduce substantially with .NET 4.0 having been released. The majority (or all) of the locking code could completely be swept away and replaced with the Concurrent data classes.

Community
  • 1
  • 1
Chris Marisic
  • 32,487
  • 24
  • 164
  • 258
  • Well I'm upset as I prefer .net platform to java, but here in java it's done without being a guru. I'm surprised ASP.NET didn't implement at least the same and even better. – user310291 Apr 27 '11 at 20:48
  • Yes it would've been a great addition to the concurrent data classes they added if they had created a generic concurrent object pool class. – Chris Marisic Apr 29 '11 at 14:02