RE: workaround and question re: profile documents in web apps Julie Kadashevich 7.Aug.00 12:26 PM a Web browser Domino Server -- HTTP All ReleasesAll Platforms
Profile docs use write once/read many algorithm. Their primary goal is to provide effecient way of of retrieving information. They are cached and extremely effecient, but they are not meant to be used as a changing global resource (e.g. counters). If you don't change your data, profile docs are the most effecient way to go. If you change your data, they maybe fast but you will not see updates to the data, so they may be unappropriate for your app.
The only thing that is guaranteed to flush the cache in 5.0x is closing ALL references (by all users if in multi-user environment) to the database. This behavior is by design, it is not a bug. The way some users are using profile docs was not invisioned by the algorithm. We recently had several discussions about introducing another type of doc with prime objective to be updatable by multiple users, rather than effeciency. We have not made a final decision on this. For a web application you can have this functionality already if you use a regular doc and use locking functions (in LS or Java) when accessing the data. You also will need to exclude the document from the view if you find it useful that profile docs are not visible.