Re: imap datasource - some design questions

I guess you can only provide what the Protocol supports.
Have you had a good look through the RFC For v4rev1 ?

http://tools.ietf.org/html/rfc3501
Interested to see how you go with it.

Cheers.

On Oct 2, 12:58 am, "Siegfried Hirsch" <siegfried.hir...@gmail.com>
wrote:
> Hi everybody
>
> I am just looking into the imap skeleton, that was provided by gwoo in the
> bin some time ago. So far I have implemented some basic read functionality.
> But now I am thinking about the further implementation of the imap
> datasource.
>
> Here are some questions, that I am not sure about:
> - should one datasource just address one mailbox on the imap server
> - what is the best primary key for imap datasources
> - after implementing read, I want to implement delete and maybe also create
> to get CRD - I dont see a need for update right now, but I am open to
> suggestions
> - what else should be taken into account implenting the imap datasource
>
> any ideas and suggestions ?
> Siegfried
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---