Frequently asked questions concerning ACAP.
Your administrator needs to be running an ACAP server, and you need to have an ACAP-enabled mail/web client. Currently there are very few ACAP-enabled mail clients, and no ACAP enabled web clients (but keep an eye on the Mozilla projects; they may add support for this). I've seen it claimed that the following support ACAP:
Contact your IT people about this (or maybe your ISP), and ensure they know about ACAP and its benefits, and ask when they're going to be using it. The front-line support people probably have no idea what you're talking about, but you may be able to find someone in the technical team who does.
Be patient with them -- there are no fully-functional Open Source servers or clients available, but you could suggest that your IT people/ISP put some time and effort into getting ACAP functioning on the 'Net. Maybe even, in a mid-to-large organisation, assign someone to help the programmers on the 'Net. You could also send encouragement to the people currently working on this (see the Resources [19] page).
Most of the rest of the information is fairly technical. The easiest to read is Dave Cridland's site (see the Resources [20] page).
Please read also the section above.
ACAP is a Internet Standard (IETF) protocol which will cut down on your support time, because you will be able to access a user's settings and change those which are incorrect, rather than having the user do that for you.
It means that you can move people more easily from machine to machine, and that the required efforts and costs for support are down, because you can access your users' settings and see any mistakes fairly quickly, once they have their ACAP connection working.
You need to set up an ACAP server and supply your clients with ACAP-enabled clients. There are a few ACAP servers out there, but all of them are, as far as I know, beta versions. Additionally, many of these are no longer developed. The only maintained ACAP server I know of is Infotrope [21]. Note that it is still in beta. But you can download it, test it, and give feedback. Helping out like this makes you truly part of the Open Source movement.
The only maintained, Open Source ACAP server is InfoTrope (see Q3, above). You could download Infotrope and test it out, although it's only in its beta stages at the moment.
More information can be found on our Resources [22] page.
ACAP is a protocol for storing program settings on a server. It specifies only the method for accessing the data, not the format of the data. The format of the data is specified in the ACAP dataset class specifications.
It means that your program can store all its settings in one place, even when your user moves from machine to machine. If you want your program to be inter-operable with others, you'll need to define a dataset class and get the IETF to approve it, but if you just want to store your settings, there's a vendor-specific area for you to use.
You need an ACAP server to test your stuff against. So you also need to download and install Infotrope. Then you can test your programs with it. You can also generate feedback, and hopefully even patches. Every problem you fix now is one that won't need to be fixed later, and every time you contribute a patch, that's one more patch you don't have to apply to the next release.
There are a range of places to help, in a range of programming languages. See the Projects [23] page for details.
More information can be found on our Resources [24] page.
Links:
[1] http://acap.jdarx.info/content/acap-faq#toc0
[2] http://acap.jdarx.info/content/acap-faq#toc1
[3] http://acap.jdarx.info/content/acap-faq#toc2
[4] http://acap.jdarx.info/content/acap-faq#toc3
[5] http://acap.jdarx.info/content/acap-faq#toc4
[6] http://acap.jdarx.info/content/acap-faq#toc5
[7] http://acap.jdarx.info/content/acap-faq#toc6
[8] http://acap.jdarx.info/content/acap-faq#toc7
[9] http://acap.jdarx.info/content/acap-faq#toc8
[10] http://acap.jdarx.info/content/acap-faq#toc9
[11] http://acap.jdarx.info/content/acap-faq#toc10
[12] http://acap.jdarx.info/content/acap-faq#toc11
[13] http://acap.jdarx.info/content/acap-faq#toc12
[14] http://acap.jdarx.info/content/acap-faq#toc13
[15] http://acap.jdarx.info/content/acap-faq#toc14
[16] http://acap.jdarx.info/content/acap-faq#toc15
[17] http://acap.jdarx.info/content/acap-faq#toc16
[18] http://acap.jdarx.info/content/acap-faq#toc17
[19] http://acap.jdarx.info/content/acap-resources
[20] http://acap.jdarx.info/content/acap-resources
[21] http://dave.cridland.net/acap/#Server
[22] http://acap.jdarx.info/content/acap-resources
[23] http://acap.jdarx.info/content/acap-projects
[24] http://acap.jdarx.info/content/acap-resources