Hi, Stipe, > Forgot another _crucial_ thing!
What about the content adaptation functionality? It seems that every new mobile device today provides "new" screen size, accepted formats and so on. Basicly there are several different tasks MMSC should be aware of when delivering the MMS message using MM1: * If the phone doesn't support the original image, convert it to the supported one (according to the phone capabilities), if possible; * If the image (in the SMIL slide) is larger than a maximum screen size of the phone, resize it; * If the phone doesn't support the original sound, convert it to the supported one (often to the AMR format) It's obvious that all these tasks will require depedency with additional graphic and audio libraries, because, for example, writing WAV -> AMR converter from stratch would be a suicide :) (3GPP provides a huge C API for that). The worst thing is that the content adaptation task can't be separated from MMSC as it's the only entity receiving the User Agent Profile (UAProf) or at least Accept headers. Shall we think about the "adapter" submodule of the mmsbox? regards, Dziugas Baltrunas
