On Tue, Oct 7, 2014 at 7:12 PM, Dominig ar Foll (Intel OTC) <
[email protected]> wrote:
> Hello,
>
> Sorry to be swimming against the flow but I do not see a car user
> configuring IMAP in a real situation.
>
I dont think it is a problem discussing various options.
>
> The initial login configuration is simple (a set of predefined profiles
> would do for most common cases) but then start the pain.
> Here is my list of questions :
> - which folders are you going to configure for auto sync at message
> reception ?
imap does not provide event for folder update what is common with
> filtering from server.
>
Usually, the user will be able to switch folder and the folder that user is
currently viewed is the one that is synced. Typically INBOX.
> - which level of history you plan to keep locally, do you need a
> configuration ?
>
NOTE: These could be app requirement, but then this is purely my thought.
I'd prefer a windowing concept. The window should have a list top 100
messages and option to go forward/back. The local history should be limited
the window. Typically users dont want a huge archive on their local
messages.
.
> search efficiency will depend of the level of available history
>
Not really, IMAP support remote search. Also, if we use Exchange, it too
has remote search iirc. Nothing is done locally.
> initial sync cost/delay will be affected by it has well.
>
Not with a small window download. The moment you open the app, the app
shows the last list of 100 messages. And fetches new messages. Once you get
the new ones, trim the window. It will not be a traditional IMAP client.
Camel has built-in support for window'ed message fetching.
- what about local copy when folder is renamed / removed from remote
> server ?
>
Will auto rename/sync.
> - what about people with multiple accounts ?
>
User can configure multiple account if needed
- strategy for address book sync ?
>
Im sure, it is already thought through by Patrick and other involved in
calendar/addressbook sync.
> - cost implication in case of tethering (most common use case) will
> quickly be out of control.
>
Yes. I agree. But this is another option.
>
>
> Honestly, I do not see that level of complexity coming soon of any real
> use in a car.
>
Being a developer related to email and Bluetooth/MAP I see the real issue.
As of today, The only commercial phone that supports email bluetooth/MAP is
blackberry (which is loosing its market share, a total different issue).
Cyanogenmod has support for it. But no other way to access your emails.
This IMAP solution becomes an opportunity to provide email on connected
cars/IVI.
> My feeling is what is needed is rather a simple easy access to the email
> already configured in the user phone.
> In my search of potential solution, I have been pleasantly surprised by
> the notification model implemented in the Tizen Watch.
>
> The user download an App on its Smart phone which register to the phone
> email event (and calendar) and push them to the remote device.
> the remote device present the incoming events and offer :
> - full read (should be voice read in a car)
> - quick response yes/no, ok/ko, driving will call back later, ...
>
I second Zoltan's thoughts. The best would be do thing via standards (MAP)
instead of custom apps.
>
> The main advantage of that model are :
> - no account configuration
> - works for mail, sms, calendar.
> - can be expended to other message based services (twitter, ...)
>
In any case a configuration is needed. Incase of a Bluetooth/MAP, the
connected device's MAP is presented for email.
Thanks,
-Srini.
> Thoughts ?
>
> Some more info on Tizen Watch notification
> https://www.youtube.com/watch?v=T8NFs0aJY7I
> http://www.engadget.com/2013/11/15/almost-all-of-your-
> notifications-can-now-display-on-galaxy-gear/
>
> Dominig ar Foll
> Senior Software Architect
> Open Source Technology Centre
> Intel SSG
>
>
>
> _______________________________________________
> IVI mailing list
> [email protected]
> https://lists.tizen.org/listinfo/ivi
>
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
