Chris Newman <Chris(_dot_)Newman(_at_)innosoft(_dot_)com> writes:
ACAP permits three architectures:
(1) ACAP and FA are tightly integrated.
(2) FA is an ACAP client.
(3) FA has a tightly integrated ACAP profile and main ACAP server provides
a referral for sieve dataset class.
Now I'm open to listing requirements for the UA to FA transfer of Sieve
scripts and seeing if something simpler than ACAP is worthwhile. Here's a
start:
* Ability to get list of FA supported Sieve Extensions
* Read/Write access to script
* Per-user storage of script
* Access control lists (for group addresses)
* Disconnected support (watch for two people editing same script)
* Authentication, integrity protection, privacy (can be provided by SASL
or TLS)
It seems that ACAP is well suited to this task, since it was
designed to handle all of the requirements you've listed
above. If this is the way to go, then we should work on an
ACAP filter dataset specification; hopefully one which will
support each of the three architectures you mention.
The UA<->FA issues can be addressed via this ACAP dataset
extension, and the Sieve effort can proceed without being
forced to worry about UA related problems.
Stan