Mid term evaluation results were posted on yesterday by Google and I have passed! Cheers! 🙂
Last week was kind of a milestone of fakeserver test journey. I could establish the communication between the calendar and the test successfully and transmit upto multiget request between the calendar and the test.
The test up-to now.
Currently the test has 2 path handlers.
- A calDav calendar was created on http://localhost/calendar and a handler was created to manage requests coming to that path.
- A path handler to serve requests to the event url which is http://localhost/calendar/event.ics
Sequence of messages flow between the test and the calendar.
- Test sends addItem() message with PUT method to the calendar.
- Calendar sends back a multiget message to retrieve calendar data with REPORT method.
- Test serves the multiget request with Schedule-tag and, etag, href address and the actual calendar data. (Now, this is where I currently stopped. multigetRequestHandler’s SAXparser throws a fatal error at the response which is believed to be due to an error with wellformness of the response.)
Here onwards things have to be dealt with cautious. After move onto add the item successfully to the calendar, operations which the schedule-tag involved in have to be implemented. For that, schedule-tag needs to be calculated according to the RFC standards. Already created the method for schedule-tag manipulation, but definitely needs more situations handled when things move on.
I use wireshark to capture the packets which are being transferred between two endpoints. This is a screen shot of the first win. 🙂
Another todo : Needs to move handler functions to separate .sjs files for more clarity. But at the moment I thought to move on leaving them in the test file.