October 2008 - calendarserver-dev - lists.macosforge.org

Re: [CalendarServer-dev] [CalendarServer-changes] [3245] CalendarServer/tags/release/CalendarServer-1.3/
by Guido Günther 17 Nov '08

17 Nov '08

Hi Winfredo, On Tue, Oct 28, 2008 at 11:21:32AM -0700, source_changes(a)macosforge.org wrote: > Revision: 3245 > http://trac.macosforge.org/projects/calendarserver/changeset/3245 > Author: wsanchez(a)apple.com > Date: 2008-10-28 11:21:32 -0700 (Tue, 28 Oct 2008) > Log Message: > ----------- > Tag 1.3. Small changes, but has been stable a while. Diffing 1.3 vs. 1.2 shows: config.py |13628 ++++++++++++++++++++++++++++++++++++++++++++++++++ static.py |16712 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- are these the only changes scheduled for 1.3? -- Guido

3 8

Re: [CalendarServer-dev] [CalendarServer] #196: Any plans to merge the pydirector changes back upstream?
by CalendarServer 30 Oct '08

30 Oct '08

#196: Any plans to merge the pydirector changes back upstream? ------------------------------+--------------------------------------------- Reporter: agx(a)sigxcpu.org | Owner: agx(a)sigxcpu.org Type: Task | Status: new Priority: 4: Nice to have | Milestone: Later Component: Calendar Server | Severity: Other Resolution: | Keywords: ------------------------------+--------------------------------------------- Changes (by agx(a)sigxcpu.org) * priority: 3: Important => 4: Nice to have Comment: Yes, moving to txLoadBalancer certainly makes sense. I pinged Anthony a while back already but never got a reply. So maybe just leaving the bug as is (in case somebody picks up the task or Anthony responds) and closing it once calendarserver moved to loadbalancer is the best thing to do. -- Ticket URL: <http://trac.calendarserver.org/ticket/196#comment:4> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #270: How should calendar discovery work?
by CalendarServer 29 Oct '08

29 Oct '08

#270: How should calendar discovery work? ------------------------------+--------------------------------------------- Reporter: agx(a)sigxcpu.org | Owner: wsanchez(a)apple.com Type: Defect | Status: closed Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Resolution: Completed | Keywords: ------------------------------+--------------------------------------------- Comment(by agx(a)sigxcpu.org) That helps. Thanks. -- Ticket URL: <http://trac.calendarserver.org/ticket/270#comment:2> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Hoping for a sanity check
by Mark Cockfield 29 Oct '08

29 Oct '08

Greetings, I am developing an RIA in Flex which needs to be built upon a calendaring foundation. After discovering that the CalendarServer is the Holy Grail I have not only found my foundation, but a good part of my infrastructure as well. Really nice work! Now imagine my disappointment upon realizing that Actionscript has been apparently locked down to only allow GET and POST http methods. After considerable thrashing about I seem to be faced with the following two options: 1. Code my own HTTP client in Actionscript at the socket level. 2. Use PyAMF and the Twisted Gateway to hook a Remote Messaging interface into the Calendar Service. As I don't really relish the thought of #1, and though I'm still fairly early in the Python/Twisted/PyAMF/CalendarServer learning curve, I think #2 might have some merit. The current line of reasoning is that in cluster.py where the memccahed and notification processes are being added to monitor a twisted gateway process could be added as well. Then in tap.py, after site = Site(realRoot), "site" could be added to the gateway as the remote object to call...? The idea being that you would simply send HTTP requsts in an array through the AMF channel to the appropriate method on the server. So what I'm hoping for is that someone might be able to tell me I am either out of my mind, or better yet, on the right track. Any thoughts would be greatly appreciated. Mark

6 15

Re: [CalendarServer-dev] [CalendarServer] #198: Consider moving to databases from files for calendar data stores
by CalendarServer 28 Oct '08

28 Oct '08

#198: Consider moving to databases from files for calendar data stores ---------------------------------+------------------------------------------ Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Enhancement | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Resolution: | Keywords: ---------------------------------+------------------------------------------ Comment(by wsanchez(a)apple.com) Files are a challenge in a couple of ways: * open/close of lots of small files adds up, and can be very expensive for reporting. * we mitigate this somewhat by using SQLite indexes * Atomicity is pretty well impossible: if I change a meeting with 100 attendees, in the current code, I'm touching 100 files. If an error occurs mid-way, we have inconsistent data which needs cleanup. I'd also like to see that for a given meeting (UID = x), that there is one master copy of the meeting, and attendees have that master copy plus their own edits. That's possible with files as well as with a DB, but my gut feel is that it will be harder with files. -- Ticket URL: <http://trac.calendarserver.org/ticket/198#comment:1> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #228: REQUEST-STATUS value incorrectly encoded
by CalendarServer 28 Oct '08

28 Oct '08

#228: REQUEST-STATUS value incorrectly encoded -------------------------------+-------------------------------------------- Reporter: cdaboo(a)apple.com | Owner: cdaboo(a)apple.com Type: Defect | Status: closed Priority: 2: Expected | Milestone: CalendarServer-2.0 Component: Calendar Server | Severity: Other Resolution: Software changed | Keywords: -------------------------------+-------------------------------------------- Changes (by wsanchez(a)apple.com) * milestone: CalendarServer-1.x => CalendarServer-2.0 -- Ticket URL: <http://trac.calendarserver.org/ticket/228#comment:5> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #227: iCal Server returns 403 when a client uses an unsupported auth method
by CalendarServer 28 Oct '08

28 Oct '08

#227: iCal Server returns 403 when a client uses an unsupported auth method ---------------------------------+------------------------------------------ Reporter: wsanchez(a)apple.com | Owner: dreid(a)apple.com Type: Defect | Status: new Priority: 3: Important | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Resolution: | Keywords: ---------------------------------+------------------------------------------ Changes (by wsanchez(a)apple.com) * milestone: CalendarServer-1.3 => CalendarServer-2.x -- Ticket URL: <http://trac.calendarserver.org/ticket/227#comment:2> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #232: digest credential db locks cause 500 error
by CalendarServer 28 Oct '08

28 Oct '08

#232: digest credential db locks cause 500 error -------------------------------+-------------------------------------------- Reporter: cdaboo(a)apple.com | Owner: cdaboo(a)apple.com Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.0 Component: Calendar Server | Severity: Serious Resolution: | Keywords: -------------------------------+-------------------------------------------- Changes (by wsanchez(a)apple.com) * milestone: CalendarServer-1.3 => CalendarServer-2.0 -- Ticket URL: <http://trac.calendarserver.org/ticket/232#comment:3> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #247: Only HTTPS ports are defined in automatically generated pydirectory configuration
by CalendarServer 28 Oct '08

28 Oct '08

#247: Only HTTPS ports are defined in automatically generated pydirectory configuration -------------------------------+-------------------------------------------- Reporter: jasper(a)shift1.nl | Owner: dreid(a)apple.com Type: Defect | Status: closed Priority: 1: Blocker | Milestone: CalendarServer-2.0 Component: Calendar Server | Severity: Other Resolution: Software changed | Keywords: -------------------------------+-------------------------------------------- Changes (by wsanchez(a)apple.com) * status: new => closed * resolution: => Software changed * milestone: CalendarServer-1.3 => CalendarServer-2.0 Comment: Fixed in trunk -- Ticket URL: <http://trac.calendarserver.org/ticket/247#comment:2> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #258: test_make_calendar_with_props fails with seed 1203447411
by CalendarServer 28 Oct '08

28 Oct '08

#258: test_make_calendar_with_props fails with seed 1203447411 ---------------------------------+------------------------------------------ Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.0 Component: Calendar Server | Severity: Other Resolution: | Keywords: ---------------------------------+------------------------------------------ Changes (by wsanchez(a)apple.com) * milestone: CalendarServer-1.x => CalendarServer-2.0 -- Ticket URL: <http://trac.calendarserver.org/ticket/258#comment:2> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0