| Hi,
PLAN A
The main obstacle that I can see is one of privileges. If an
unprivileged user grants access to another user, then the granting user
will probably not have READ access to the other user's FILECAB.DAT,
let alone the WRITE access you would need.
So I think you could create a data file that has a list of
entries containing drawer name and user name pairs. Then a privileged
user would be able to run a program that for each entry writes a new
record to the FILECAB.DAT of the appropriate user.
Another problem to solve is what the (unique) NAME field is to be in
FILECAB.DAT. If two users have a drawer called TEST, then you'll have
to come with a scheme where the second one is called something like
TEST1.
Lastly you you will need to consider what happens if a user shares with
a group, or the special *LOCAL and *WORLD groups.
HTH
PLAN B
A different approach might to make use of mail functions. You can
customise your system to add another mail function. You could compose a
mail message that would be sent to the sharees, and when they receive
and read it they will be put in something like the ADR form. However I
don't think think this approach would work for TeamLinks users. A
similar approach useing TeamRoute might, but I don't suppose you've got
TeamRoute installed on the ALL-IN-1 system.
HTH
Stuart
|
|
As far as the auto ADR I would say, you would come up with more
problems than you would solve, Stuart mentions alot of them. I do like
the mail suggestion, just send mail to all IOS users on the system
and tell them a new drawer has been made available, Trying to
pick the users given access ot would be hard. You would have to
consider groups, world access, local access etc. Next to imposisble
to do so. Also what if a user doesn't want the drawer in his FC?
Another point to consider is if you have hte DSO installed, you have
no chance of getting it to work. THe remote users filecab.dat file
will be on the remote system, and you have absolutely no way of
effectively mapping a proxy backwards, not to mention if the proxy
was into OAFC$DEFAULT (world access).
If you have to do it do the mail routine way.
You could also push for an IAD available from the PC. The historical
reasons for it not being there are almost nil given the current state
of DNS. It would never have a chance at making it into V2 of TeamLinks
but I think it should be done.
--Bob
|