Thank you for choosing Steltor's Calendar API (CAPI). These release notes contain known limitations and problems with the product. For installation instructions, see the Readme file. For general questions and troubleshooting information about CAPI, see the FAQs available on the Steltor Web site.
Use of this software is subject to the terms detailed in the license agreement.
Contents of this file
- System requirements
- How to report problems
- What's new in this release
- Limitations, caveats and known problems with this release
System requirements
One of the following Steltor calendar servers:Please note that older calendar server versions may not be able to take advantage of all CAPI functionality.
- CorporateTime Server 4.0 or greater (5.1 or greater recommended, certified against 5.2)
- Lexacom Calendar Server 4.0 or greater (5.1 or greater recommended, certified against 5.2)
- Lexacom Enterprise Calendar Server 5.1 or greater (certified against 5.2)
This version is certified against the following platforms:
- SPARC Solaris 2.6 (using Sun's recommended patches from 21 February 2001 and Sun Workshop 5.0)
- HP-UX 10.20 (using cc version A.10.32.30 and aCC version A.01.23)
- IBM AIX 4.3.3 (using VisualAge C++ 5.0)
- Red Hat Linux 6.1 (using egcs-2.91.66 19990314/Linux (ecgs-1.1.2 release) compiler)
- Microsoft Windows NT 4.0 (using MSVC 6.0)
How to report problems
Contact Steltor's technical support department at support@steltor.com or call (514) 733-8500.
What's new in this release
- Performance enhancements when storing and fetching multiple events with common attendees through e-mail and formatted name caches.
- Fixes for memory problems when destroying streams or when storing large numbers of events in a single CAPI_StoreEvent call.
- CAPI 2.0.1 respects the calendar server limit on instances of recurring events.
- CAPIFetchEventsByRange no longer filters out VALARM components.
- CAPIFetchEventsByID now validates the iModifier parameter.
- New GNU makefiles to build demo programs on UNIX platforms.
- New MSVC workspace files to build demo programs on Windows platforms.
- Solaris version of libcapi.so built using a compiler with more recent patches (Sun's recommended patches as of 21 February 2001) for greater compatibility with Sun Workshop 5.0.
- Bug fixes in demo programs.
- Corrected values for CAPI_THISINSTANCE, CAPI_THISANDPRIOR and CAPI_THISANDFUTURE in the Miscellaneous section of the Reference Manual.
New in CAPI 2.0
Expiration: This build will not expire.
- Improved performance: New caches improve the speed of storing and fetching events.
- CAPI_Connect: New function that connects to a calendar server without authenticating.
- CAPI_CreateFileStream, CAPI_CreateMemoryStream, CAPI_CreateCallbackStream: New functions that provide alternate and more efficient stream management.
- CAPI_DeleteEvent: New modes to allow e-mail and wireless notification on event deletion.
- CAPI_GetCapabilities: New function replacing CAPI_Capabilities.
- CAPI_GetStatusLevels: New function to break down a status code into its constituent bit fields.
- CAPI_GetStatusString: New function that returns a text description for a given status code.
- CAPI_Logoff: New mode to log off without disconnecting from the calendar server.
- CAPI_Logon: Can now specify ACE mechanisms and ports through the host argument, and can specify domain names through the user argument. Also supports cluster environments with master nodes. The session parameter may be null, which creates a new session, or may specify an existing session created through CAPI_Connect or CAPI_Logon.
- CAPI_SetIdentity: New function that allows the authenticated user to work as a designate for another user.
- CAPI_StoreEvent: New modes to allow e-mail and wireless notification on creation and modification; support for e-mail and wireless reminders through VALARMs.
Limitations, caveats, and known problems with this release
Pre-4.0 versions of CorporateTime Server
Versions of CorporateTime Server before 4.0 do not fully support Internet standards extensions. Details of the limitations are included in the reference manual.Solaris C++ compiler
For binary compatibility with Steltor's standard shared libraries, users with Solaris platforms must have the native Sun C++ compiler installed.