Blog

Blog Search

Search this site

Advertisements

Everything Else

Sponsor

Wood Watch Review

Google Custom Searches

Custom Blogger Search
Custom Sametime Search
Custom XPages Search

Subscribe

Subscribe via RSS

Recent Tweets

Hosting by

You are here: Home › Blog

An update on DWA issue two days ago from a reader


Tags :


Stephan Wissel came forward with a comment on how they handle the issue of local address books.  I thought it was interesting and deserved some discussion.

Hi Chris,
since R6 it is official that the users names.nsf can live on a server (a.k.a. Roaming profile - We did that for backup since R4). With a little scripting help we do:
a) synchronize the users NAB with the Names in the mailfile automatically (user doesn't even know that they would need to do so)
b) Filter out the names from the public NAB. Here we tried two strategies: either remove them from the users NAB (which p***d some users off) or exclude them from the sync with the mail file.
Hth
:-) stw

So he is saying with the roaming feature enabled in Domino 6, they are pushing names to the mailfile in the background with scripting or filtering out public address names.  I fully agree with the second choice for a couple reasons:
  1. If the user is utilizing Domino Web Access (DWA) then why would they need the public addresses in the personal address book?  The server has that directory as an option.  Sure, we could go so far as to say DOLS, but why not then give them the public directory in DOLS also?  Makes sense to me.
  2. If you filter the names from the public NAB and then push a mobile directory catalog for users requiring it, you guarantee updated names, addresses and encryption keys for all users.  Plus doing this on the server side (could be a strictly roaming server for scaling reasons) would take the user end scripting out of the picture also.  A nightly scan could be done.  Once again some would say they store possible personal or additional information in the local listing for another employee that you would not want or shown in the public listing.  So let's just make the filter match the public listing and even match the public key.  All would be satisfied that way.

I guess where we are heading in all this is the option to guarantee that addressing will not fail and there will not be those weird names when addressing from the web in DWA.