private Hashtable versus Cache

Results 1 to 2 of 2

Thread: private Hashtable versus Cache

  1. #1
    Join Date
    Dec 1969

    Default private Hashtable versus Cache

    Hi,<BR><BR>i&#039;ve been looking at the microsoft data access application block code, and noticed that they store all of the parameters in a private hashtable.<BR><BR>Can anyone please explain what the advantage is of storing them in a private hashtable over normal cache? <BR><BR>Further to this, if you have a large system, with say 150 stored procs, quite a few of which won&#039;t be used that often, surely cache would be better as it manages itself in terms of getting rid of items that haven&#039;t been used for a while, as opposed to a private hashtable that doesn&#039;t appear to do this.<BR><BR>Thanks for any comments,<BR><BR>Andy

  2. #2

    Default RE: private Hashtable versus Cache

    I dont think that we have the same easily accesible cache when building Windows apps that we have for ASP.Net<BR><BR>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts