These three tasks below are related, and I can help provide some context since I'm currently working on Interop.

3. Find out about teleport with public beta
 - what needs to be done to teleport? is it based on teleport strawman?

4. OGP tests
- should be starting to write documentation on the Login (just login?) protocols and how they should be tested (Infinity has started on this. Link to the page?) - should be tests for agent domain - region domain (sim) communication. In particular, we should
   have tests written for request_rez_avatar
 - auth.py tests?

5. Collaborate with Interop
- we need to get in contact with interop more to get more detailed information about what they
    want and how they intend to use Pyogp

The final protocol will be defined here: https://wiki.secondlife.com/wiki/SLGOGP_Draft_1 (Needs to be renamed to OGP) but for now, Zero is a little behind so everything pending to be in the OGP is implemented against the strawman: https://wiki.secondlife.com/wiki/SLGOGP_Teleport_Strawman

Tests should be written against the OGP/Strawman, which currently includes login and teleport, which includes auth.py as well as rez_avatar/request (see strawman). Although OpenSim does not use rez_avatar/request *yet* it *will* for the July 31st Beta, so these tests need to work against the protocol, and so does the OpenSim code.

Apologies for the late documentation on this, but I've just pulled in the internal flow chart into the Strawman which includes details on auth.py. https://wiki.secondlife.com/wiki/SLGOGP_Teleport_Strawman#Login
6. Start on messaging system
- find out the true scope of the messages that will be sent, the ways we need to serialize, what components we will need to get this done (Builder, Parser, Reader) - write tests for how we want this to be used (this may be hard at this point because we don't
    know scope)
 - write tests for the current parser
 - refactor the parser to follow the "NEW" coding standard we adopted
 *- network layer swapability*
So far, only legacy stuff requires UDP messages, and we're working on trying to get rid of them for the OGP. Most of what happens during login is handshaking to set up the UDP messaging system, but we want to concentrate on the HTTP messages via Caps for OGP testing.

7. Agent Domain
 - Tao has been working on writing an agent domain
 - blocked by his inability to connect to our regions

8. Task tracking
 - pjira, or some other form

9. Refactor the wiki
 - what part of the wiki is poor as it currently is?
- reword the stuff in the test harness page to make it clear that we won't be building a framework, but simply using a framework (PyUnit, doctest, py.test) to create test suites for both the client lib AND servers running OGP protocols - check out Enus' layout https://wiki.secondlife.com/wiki/User:Enus_Linden/Project-Wiki-Structure

*10. Test harness
 - get testing set up for the test harness (similar to bin\test)
 - move test_ogplogin.py to the test harness side*

_______________________________________________
Click here to unsubscribe or manage your list subscription:
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp
_______________________________________________
Click here to unsubscribe or manage your list subscription:
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

Reply via email to