From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1ea92c0e5255811d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-03-02 04:06:33 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!newsfeed.telusplanet.net!ps01-chi1.MISMATCH!chi1.webusenet.com!news.webusenet.com!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny02.gnilink.net.POSTED!53ab2750!not-for-mail From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030131 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Container libraries References: <5d6fdb61.0302250317.c49d71a@posting.google.com> <1046214593.420402@master.nyc.kbcfp.com> <8db3d6c8.0303020106.157c6aa8@posting.google.com> In-Reply-To: <8db3d6c8.0303020106.157c6aa8@posting.google.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Date: Sun, 02 Mar 2003 12:06:32 GMT NNTP-Posting-Host: 162.83.246.225 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny02.gnilink.net 1046606792 162.83.246.225 (Sun, 02 Mar 2003 07:06:32 EST) NNTP-Posting-Date: Sun, 02 Mar 2003 07:06:32 EST Xref: archiver1.google.com comp.lang.ada:34794 Date: 2003-03-02T12:06:32+00:00 List-Id: steve_H wrote: > But this way you will have duplication of effort. Each client/application > who wants to use the container needs to add code to provide the synch. outside > the container. > > What one can do is provide 2 versions of the container, one that is synch. and > one that is not. If the client knows there will be one task only who will > access the container, then use the non-synch. version (which is assumed > to be a little faster), else use the other. No. What you are missing is that synchronization is rarely needed for one container. Instead, an application has a variety of data that must be maintained consistently. That is why synchronization belongs with the application rather than with the container.