mms: next steps

mms: next steps

[Ronald Tessier]

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

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

Re: mms: next steps

[Marcel Holtmann]

[-- Attachment #1: Type: text/plain, Size: 931 bytes --]

Hi Ronald,

> 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,

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.

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

Sounds like a good thing to add now.

> - 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