Hi! > > I've been quiet, developing a plugin for the Solaris calendar server > > (actually the CDE Calendar Server). N.B. Not the SunONE calendar server, > > but the CDE 'dtcm' calendar. - csa_plugin as the library on which it > > depends is called 'csa'. > > > > It's still beta; i.e. it works for me!
Cool! I could give you access to the SourceForge project so that you can check it in. Do you have a login at sourceforge? > > Couple of quick questions for you: > > > > 1. If I set always_connected to true in the plugin, will multisync > > loop around after some pre-determined timeout to re-scan the > > endpoints ? If always_connected is true, then MultiSync will try to connect once (using sync_connect()) and then keep that connection alive. If not, MultiSync will connect and close for every update (if not notified otherwise, periodically as set in the sync pair options). So in your case, if the database will generally always be available(?) so you should set always_connected. > > What I haven't tested, is whether the VCal I create is really > > valid against something that understands VCal entries, and > > whether the VCal -> CSA is robust enough/able to accomodate > > enough of the VCal spec. > > > > I've been working with RFC2445, so the VCal should be ok; but > > it will need some testing and probably tweaking! Good! If you have the opportunity, please try it again Evolution and see that it works there. This is our standard benchmark. Also, since feel free to use [EMAIL PROTECTED] for any developer related questions or discussion. /Bo ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Multisync-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/multisync-devel
