The new schedule and the revised proposal is at
https://sites.google.com/site/bogdanciprian/gsoc2010

For archival purposes I include the schedule also on the ML:

April 26 – May 23:

    * bonding with the community
    * getting to know the formal aspects of developing for apache in
the GSoC context (VCS or patches, infrastructure, etc)
    * investigating further the Vysper project
    * prototyping

May 24 – June 6 (2 weeks):

    * integrating Jetty into Vysper
    * implementing the parsing (reusing existing components from Vysper)
    * interpreting in a Handler the session creation request and
creating a context for the session (possibly a subcass of
AbstractSessionContext)
    * SSL filter handling for configured TCPEndpoints with SSL

June 7 – June 27 (3 weeks):

    * implementing the logic of responses to the client (keeping a
session before sending an empty response on timeout, honoring the
'hold' attribute for requests,  acknowledgment 'ack' attribute  logic,
keeping the responses in some cache to be able to resend them if not
acknowledged by the client)
    * implementing session creation response
    * sending back responses to the client containing stanzas from Vysper
    * implementation of SASL negotiation for user authentication and
resource binding
    * implementing pause (inactivity)
    * extracting stanzas from the payload and sending them to the
StanzaProcessor in Vysper

June 28 – July 11 (2 weeks):

    * by now the implementation should be workable, test the
implementation with the javascript libraries and solve any issues may
arise
    * start the implementation of the web-application based on Strophe.js

July 12 – July 25 (2 weeks):

    * complete the web-application and validation of the implementation with it
    * resolve any other issues discovered when building the web-app
    * writing the documentation: User Guide on how to use Vysper with
Javascript BOSH libraries and Deployment Guide with common problems
for deployment to restricted environments and limited clients

July 26 – August 8 (2 weeks):

    * if there are any other issues or unfinished tasks, then solve them now
    * as the time permits (if there are no pending issues or
unfinished tasks) implement: dynamic script tags and WebSocket API
transports.

August 9 – August 16 (1 week):

    * resolve any left issue



Bogdan

Reply via email to