Composite UI application Block - Thread Safe?

  • Thread starter Thread starter lwhitb1
  • Start date Start date
L

lwhitb1

Does anyone have any input on setting up my CAB application so that the
application is thread safe, and cached appropiately? I read that this
can be managed through Services, and dynamic injection. On the
contrary, I was told that this can be handled using Enterprise Library
cached application block. Last, but not least, i read you can implement
this at the class level, creating immutable classes, and caching them
accordingly. Any suggestions would be greatly appreciated?
 
Thus wrote lwhitb1,
Does anyone have any input on setting up my CAB application so that
the application is thread safe, and cached appropiately?
Click to expand...

I'm a bit puzzled what a thread-safe *application* might be and how it relates
to caching. What are you trying to achieve?

Cheers,
 
I'm new to the composite ui application block, so forgive me if
something i say is not completey clear, for i'm still trying to figure
it out. I'm building a CAB application that displays information to a
user from a sql service data layer. I'm building the data layer, and
i'm confused about how I should create the classes. I would like for
the classes I use within the CAB application to be instantiated once,
and use that instance till it changes. Now these static classes need
to be stored somewhere, and for that reason I mentioned caching, for i
figured they would need to be cached in a collection of some sort. They
need to be thread safe so that when they do change, the references to
them won't get screwed up. Now, I have been reading up on CAB, and it
appears as though this can be achieved in a number of ways. For
example, the objectbuilder probably manages these things under the hood
for the models/views and components. Also, you can use existing
provider patterns like the cached application block, dynamic injection,
singelton. etc.. This is where i'm getting lost.. Should I even worry
about creating thread-safe classes at the data layer, and just send the
information to the upper tiers, so that CAB can manage them, or should
i just create a class that is immutable or something at the data layer
level. I guess what i'm trying to say is.. What is the best way to
create the data layer, and pass the data up to a service or view in the
CAB framework..Makes sense? Let me know if I need to clarify anything
...

Thanks for the reply..
 
Back
Top