tor, 2004-07-15 kl. 15:21 skrev Stipe Tolj: > ok, here are my comments. I did code the mmsbox on Wapme site ;)
Is that going to be released into Kannel? > > mmsbox decodes the MMS to an RFC-822-format mail. > correct, MMS Encapsulation is similar to WSP headers. Bring the > messages to an internal representation (we cann it MMSEncap) and use > functions to convert to MIME. MIME code is partly integrated into > Kannel already (AFAIR). Actually, I have a very specific reason to convert it to RFC822-format. I'll get to that. > > mmsbox relays decoded MMS to an SMTP server. > correct, in case the recipient is addresses via an email address. You > should think of having an exim module that can "dock" to Kannel or > your mmsbox. No, actually, I'll always send it to an SMTP server. > > If it's a local user, the SMTP server somehow relays the mail > > back to the mmsbox. > why this? Because doing so gives a few advantages, as I see it: 1. A message coming from either MM1 or MM4 comes into the MMSC from the same channel. This eases the implementation. At least, that's the theory. :-) 2. I think it'd be TOTALLY overkill to implement a complete MMS routing engine into bearerbox, considering that MMS transport is almost the same as SMTP. Using the architecture I've outlined, all your MMS routing is done in your mail server of choice. > bearerbox is supposed to be the "routing engine" for Kannel. Hence let > the mmsbox pass the MMS message in Kannel msg representation to > bearerbox and let bearerbox decide to which MM4 link the messages is > transported. I just have kind of a problem with implementing an SMTP routing engine in Kannel when there's so many mail servers out there that do a great job. > > mmsbox sends notification to recipient with the appropriate > > message ID. > correct. Therefore you can utalize 2 ways: a) mmsbox acts as PI (push > initiator) towards PPG (wapbox). This is the "architecturely clean > way". That was definitely my plan! > > Kannel receives request for URL. > > Message ID from URL is used to look up mail from IMAP storage > ok, in case you use an mbox format mail spool directory to actually > "store" your MMS localy, you can utalize IMAP for this. mbox, maildir, MySQL, whatever my IMAP server understands, yes. > But why this overhead? AHA! I was hoping someone would ask. :-) Because that way, you can have a web interface to your MMS inbox, you can use your regular e-mail client, etc. Although, I just remembered that the format that is sent via MM4 is the binarily encapsulated format, right? It's not RFC-822, is it? Oh, well, I'll have to think a bit about how to send stuff via MM4, then. Besides, loads of VERY good SMTP servers and IMAP-servers exist, so it'd be a shame to start making either from scratch. > You missed some things that come with the "advanced version": [snip] Right. For now, I'm just focused on getting the most basic functionality done. > correct. mmsbox can be treated as a "local MM4 link". As the home MMSC > in this sense. By letting bearerbox decide on the routing, you can > connect several mmsboxes to bearerbox which represent MMSC > implementations of varios carriers/netwoks and let bearerbox connect > using the same abtrasction API to MM4 implementations, like SMTP or > SOAP/XML over HTTP in some cases (actually this would be MM7 in the > MMS overall architecture, and the receiving MMSC would see you as a > VASP application). Wow. You totally lost me there. I went to a concert yesterday, so I'm not quite at 100% yet. :-) > > This setup is MUCH more complex, adds a lot of internal network traffic, > > BUT gives a lot of control back to the bearerbox, where I believe it > > belongs, right? > +++1. It steamslessly integrates Kannels routing, queueing and storing > architecture to the MM1, MM4, MM7 links defined in the overall MMS > architecture. Right. I'm not THAT familiar with the internal magic of Kannel, so this'll take quite a bit of extra time, as I need to: j1. Figure out how stuff works now. 2. Figure out how to make it do what I need. Time well spent, but extra time nonetheless.. > ok, first of all: mmsbox does exist. Exactly with the architecture I > described above. It lives in cages at Wapme. And it _may_ be released > to Kannel free land sometime. Ok. My life is just a bit too short for that. :-D > And about the convince: Simply tell him it puts your company in > control of developing the software components you _really_ need and > other people are contributing to this effort with no financial > demands. And what did YOUR employer respond to this? :-D > Now, as a lot of people are "thinking" of implementing MMS support to > Kannel, and Kannel as itself is designed for messaging, it's really > annoying me that I can't drop the code out of the door and let people > work on it... I'll try to see how far I get from the management side > here to get this done. Looking forward. A lot! -- S�ren Hansen <[EMAIL PROTECTED]>
