Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best practices for webcal clients and servers #37

Open
dmfs opened this issue Sep 28, 2017 · 2 comments
Open

Best practices for webcal clients and servers #37

dmfs opened this issue Sep 28, 2017 · 2 comments
Assignees

Comments

@dmfs
Copy link
Member

dmfs commented Sep 28, 2017

As a developer of a server which can render webcal feeds or of a client which can consume webcal feeds, I'd like to have some guidance. Possible topics:

  • use and meaning of iCalendar METHOD property
  • content-type
  • Etags
  • if-none-match header
  • subscription upgrade
  • best practices for clients
    • how to "discover" good behavior on a server
    • how to deal with bad behaving servers
  • common pitfalls
    • why not to return "current time" as "last modified"
@wsdwl
Copy link
Member

wsdwl commented Jun 7, 2019

I would say, that beyond the last point, I assume this issue to be solved by copying Everts documentation about how to build a Card/CalDAV client to DEVGUIDE with the latest commit.

@dmfs : What's your opinion?

@dmfs
Copy link
Member Author

dmfs commented Jun 7, 2019

My request was about Webcal feeds, not CalDAV. I didn't check the new content yet, but afaik Evert didn't address webcal feeds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants