I am using sabre/dav: 3.1 and I have my own backend that extends the abstract backend: class Backend extends \Sabre\CalDAV\Backend\AbstractBackend
In looking at the AbstractBackend.php, it implements BackendInterface. However, this doesn't include SchedulingSupport methods, which extends BackendInterface and thus is a superset of everything in BackendInterface. Given my situation with a custom backend, is there a way to utilize the abstract backend but still implement scheduling support (i.e. the equivalent of abstract class AbstractBackend implements SchedulingSupport -- without having to change the sabre code. I think i can do something like this: class Backend extends \Sabre\CalDAV\Backend\AbstractBackend implements \Sabre\CalDAV\Backend\SchedulingSupport Note - The reason I am trying to implement scheduling support is because on iOS, we have never been able to accept/reject calendar invites, whereas on all other clients it works - even mac os x calendar, without scheduling support. Thanks! -- You received this message because you are subscribed to the Google Groups "SabreDAV Discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to sabredav-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sabredav-discuss/3c17878d-b0bd-40e0-bd7b-7fdd66ef8892%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
