Skip to contentSkip to conversation

mms: next steps

DISCUSSION Ronald Tessier 2 participants 2 messages May 4, 2012 – May 10, 2012

lore
Share & tools
lore
#0 lore raw

Hi Marcel,

Now that mms' TODO is almost empty (I've sent a set of patches yesterday that implement the last entry of the TODO).
What should we add to release a first version of MMS ?

What's already in place :
- MMS submission,
- MMS reception (automatic retrieval support),
- MMS storage with status support,
- (Basic) error management with transaction completion on restart.

What can be added :
- Manual retrieval support for MMS reception,
- Delivery report support (M-Delivered.ind),
- Enhance D-Bus API (DeleteMessages(), DeleteConversation() ...)
- or something else ...

How do you see the next actions to take?

Thanks in advance for your feedback.
Best regards,

Ronald

#1 lore raw

Hi Ronald,

Quoted 4 lines

Now that mms' TODO is almost empty (I've sent a set of patches yesterday that implement the last entry of the TODO).
What should we add to release a first version of MMS ?

Quoted 8 lines

What's already in place :
- MMS submission,
- MMS reception (automatic retrieval support),
- MMS storage with status support,
- (Basic) error management with transaction completion on restart.

What can be added :
- Manual retrieval support for MMS reception,

I think we should not do that. Manual has never been a good idea. Lets try to just have proper error recovery and do this without user interaction.

Quoted 1 line

- Delivery report support (M-Delivered.ind),

Sounds like a good thing to add now.

Quoted 1 line

- Enhance D-Bus API (DeleteMessages(), DeleteConversation() ...)

Send proposals for this. Sounds on the first look reasonable. However the devil might be in the details.

Regards

Marcel