mmsconf.h

彩信MMS的全部代码

 * presentation will not be able to find the modified entry header.
 * - FALSE means that the message is considered to be corrupt.
 */
#define MMS_USE_MAX_ENTRY_HEADER        TRUE

/*! When the MMS Client is configured to send to an MMS 1.0 MMSC, the read 
 * reports are sent as ordinary messages. These can be created either in the 
 * Drafts folder or in the Outbox folder. This definition determines where they 
 * will be created.
 *
 * Possible values
 * - TRUE means that MMS 1.0 Read Reports are created in the Outbox
 * - FALSE means that MMS 1.0 Read Reports are created in the Drafts folder
 */
#define MMS_CREATE_1_0_READ_REPORT_IN_OUTBOX    FALSE

/*! When the MMS Client is configured to send to an MMS 1.0 MMSC, the read 
 * reports are sent as ordinary messages. This definition determines if the 
 * v1.0 Read Reports will be saved in persistent storage after they have been 
 * sent.
 *
 * Possible values
 * - TRUE means that MMS 1.0 Read Reports are saved after sending
 * - FALSE means that MMS 1.0 Read Reports are deleted after sending
 */
#define MMS_SAVE_1_0_READ_REPORT        TRUE


/***************************************************************************
 * Defines related to the report file handling 
 **************************************************************************/
/*! The maximum number of requested reports that the MMS Client can keep in 
 *  the report file. */
#define MAX_NUM_OF_REPORT_STORE     32

/*! Max length of the Message-Id field */
#define MAX_MESSAGE_ID              40

/*! Category for the delivery/read report file */
#define MMS_FILE_CATEGORY_RPT       ((char)'K')

/*! Category for storage of immediate retrieval notification files. */
#define MMS_FILE_CATEGORY_IMMEDIATE ((char)'L')

/*! Category for storage of logs. */
#ifdef MMS_LOG_PROTOCOL
#define MMS_FILE_CATEGORY_LOGGING   ((char)'N')
#endif /* MMS_LOG_PROTOCOL */

/*! Category for import files. */
#define MMS_FILE_CATEGORY_IMPORT    ((char)'O')

/* The following definitions are used to determine operations that will
 * cause the notification table (used to detect notification duplicates)
 * to be written to persistent storage.
 * If a specific operation should cause the file to be written, assure that 
 * it is defined. Otherwise, assure that it is undefined (e.g. 
 * #undef MMS_NOTIF_TABLE_SAVE_CREATE).
 */
#define MMS_NOTIF_TABLE_SAVE_CREATE   1   /*!< Save table when notif is created */
#define MMS_NOTIF_TABLE_SAVE_DELETE   1   /*!< Save table when notif is deleted */

/****************************************************************************
 * Memory related configuration definitions. The defines below determines how 
 * the MMS Client uses memory. Please read the manual for a longer description 
 * of them. All sizes for the following definitions is given in bytes.
 ****************************************************************************/

/*! Defines the maximum size of a pushed notification. If the notification is 
 *  larger than this value, the notification cannot be handled. A value of 
 *  300 is sufficient in most cases. 
 */
#define MMS_MAX_NOTIFICATION_SIZE   512

/*! Maximum size of a POST message before it is divided into multiple 
 * MMSa_http calls towards the HTTP/WSP stack. This define can not be less 
 * than the largest possible MMS PDU header. Our recommendation is to never 
 * have itless than 512 bytes. It is recommended that the same PDU size is 
 * used in the HTTP/WSP stack. When using MIC, this definition must not be 
 * larger than 2.5 kB. Please refer to the MIC manual and the function 
 * MICc_httpRequest. The definition must not be larger than 
 * #MMS_MAX_CHUNK_SIZE.
 */
#define MMS_POST_MAX_SIZE           2560

/*! Defines the maximum size of a allocation of a chunk. Larger data items will
 * be stored on file. If chosen to small, all messages cannot be handled, e.g.
 * if the MMS header does not fit within one memory chunk. */
#define MMS_MAX_CHUNK_SIZE          4096UL

/*! If the generic memory allocation routines are used (i.e. #USE_G_MALLOC is 
 * defined in cmnconf.h), this is the maximum dynamical memory that the MMS 
 * Client is allowed to use. Our recommendation is to set this value larger 
 * than the largest of:
 *  - 8192 bytes
 *  - 8 * #MMS_MAX_CHUNK_SIZE 
 * However, the memory size must never exceed 128 kB.
 */
#define MMS_MALLOC_MEM_SIZE         (8 * MMS_MAX_CHUNK_SIZE)

/*! Define the size of the buffer used to store SMIL messges while creating
 *  a SMIL. Larger data items will be stored on file. Note, if the SMIL create
 *  module is included in the MMS application this buffer must have a value.
 *  The absolute minimum size is 50 bytes. Recomended minimum is 250 bytes.
 */
#define SMIL_CREATE_BUFFER_SIZE          2048U

/*! The MMS SMIL limited the content-id or content-location to 100 (us-ascii) 
 * characters.
 */
#define SMIL_MAX_MEDIA_OBJECT_SRC_LENGHT 100

/*! The max number of regions allowed in creating an MMS SMIL. MMS SMIL allows 
 * at most two (2) regions named 'text' and 'image'. As long as this define is
 * two the region id's name will be checked and only allowed to be either 
 * 'text' or 'image'. 
 */
#define SMIL_MAX_NUM_REGIONS 2

/*! Time in tenth of seconds before the parse handling operation 
 * is considered have timed out e.g. a value of 300 means 30 seconds.
 * The time is mesured from calling the parser for the first time to
 * all data has been delivered and the parse handler returns OK. 
 */
#define SMIL_PARSE_HANDLER_TIMEOUT             300

/*! SMIL parser handler (SPH) buffer used to send data to parser. 
 *  Recommended minimum value of 100 bytes, 
 */
#define SMIL_SPH_BUFFER_SIZE 2048

/*! The maximal nesting allowed for a SMIL message when processed by MMS 
 *  Client's SMIL parser handler (SPH). (Value also sets the size of 
 *  SPH internal int stack). Recomended minimum value is 15.
 */
#define SMIL_SPH_MAX_NESTING_DEPTH 15

/*! Keyword versus numerical RGB representation of colors. Default according to
 *  [W3C CSS 2.1 spec, Section 4.3.6 'Colors']
 */
#define SMIL_COLOR_SET {\
    {"white",   0xFFFFFF},\
    {"silver",  0xC0C0C0},\
    {"gray",    0x808080},\
    {"black",   0x000000},\
    {"yellow",  0xFFFF00},\
    {"fuchsia", 0xFF00FF},\
    {"red",     0xFF0000},\
    {"maroon",  0x800000},\
    {"lime",    0x00FF00},\
    {"olive",   0x808000},\
    {"green",   0x008000},\
    {"purple",  0x800080},\
    {"aqua",    0x00FFFF},\
    {"teal",    0x008080},\
    {"blue",    0x0000FF},\
    {"navy",    0x000080},\
    {NULL,      SMIL_COLOR_NOT_USED}}

/****************************************************************************
 * Defines for an alternative TDA interface.
 ****************************************************************************/

/*! If not defined, some connector and adapter functions are disabled to 
 *  minimize the number of functions needed to implement in the TDA. This 
 *  will however give the MMS Client less functionality. */
#define MMS_STANDARD_INTERFACE

/*! If defined, data sent to the MMS adapter functions 
 *  MMSa_getConfigStrResponse, MMSa_deliveryReportReceived, 
 *  MMSa_getBodyPartResponse, MMSa_getMessageResponse, 
 *  MMSa_getMessageIdListResponse and MMSa_readReportIndication 
 *  will not be freed by the MMS Client after the call. Instead the adapter 
 *  functions or the MMS Application must free the data using the functions
 *  freeMmsAddress, freeMmsReadOrigInd, freeMmsCharStr, freeMmsBodyPart,
 *  freeMmsMessagePart and freeMmsMsgIdList.
 */
#undef MMS_RETAIN_ADAPTER_PARAMETERS

/*! If defined, comma separated addresses will be considered as separate
 * addresses during parsing, e.g. a To address with the following value
 * "[phone]/TYPE=PLMN, [phone]/TYPE=PLMN" will be divided into two
 * address entries. Comma separated addresses are not allowed according to the
 * MMS standard but there exists products that send addresses this way so
 * by accepting these, the MMS Client will correctly parse those addresses.
 */
#define MMS_ACCEPT_COMMA_SEPARATED_ADDRESSES

/*! If defined, the external DRM ID generation will be enabled. This will also
 *  leed to changes in the structure of the info files of the messages. 
 */
#undef MMS_EXTERNAL_DRM_ID_GENERATION

#endif /* _MMSCONF_H */