Difference between revisions of "Pyogp/Design Decisions"

From Second Life Wiki
Jump to navigation Jump to search
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==ZCA==
==ZCA==
===Arguments===
#ZCA allows decoupling. You can simply ask for any class that provides an interface, rather than directly calling that class (and therefore needing all the imports to do so). If you wanted to change, say, the class name, you would have to change all the imports and references to the name. Using ZCA, you can just change the name and keep the interface, it will do the same.
#No reinventing the wheel – global registry - zca allows global registration of things like utilities (singleton class that provide some functionality), event subscriber registration, etc. In order for this to happen, need to use ZCA interfaces, adapters, and utilities.
#Cleaner code – forces you to define interfaces, and the adapters that use those interfaces. However, this can be done outside of zca. Interfaces exist outside of zca. In fact, zca doesn’t enforce interfaces because Python is dynamically typed language. We can do this (enforce coding to interfaces and using documentation) without ZCA, but we then lose the ability to register with the global registry.
#ZCA needs Python 2.4 to run. This is not a problem unless older versions of Python are going to be used with Pyogp.


===Examples:===
=== There is no ZCA in pyogp ===
#Network layer – swapping the way the client connects to the servers
#*Urllib2, eventlet, mock objects
#Packet event handling – we can have packages of packet subscribers. When these packages are included, or used by ZCA, the packets will get handled. If we use a different package, the packets will get handled differently. Allows us to define multiple ways to handle packets. Also allows us to test packets by having the tests be a subscriber and in a package as well.


==Buildout==
==Buildout==
It is being considered whether we want to do away with buildout. Perhaps some day we shall, but it works, and there is no urgency.
===Arguments===
===Arguments===
#Setting up path – we can use buildout to setup our path automatically for development. Without buildout, we would have to set the path ourselves, which would be difficult because of the dependencies and the relation to the system we are on.
#Setting up path – we can use buildout to setup our path automatically for development. Without buildout, we would have to set the path ourselves, which would be difficult because of the dependencies and the relation to the system we are on.
#Setting up the environment – can use buildout to automatically fetch the dependencies we rely upon (downloading eggs, getting svn projects, etc)
#Setting up the environment – can use buildout to automatically fetch the dependencies we rely upon (downloading eggs, getting svn projects, etc)


[[Category:Pyogp]]
[[Category:Pyogp]]
[[Category:Pyogp_Kitchen_Sink]]

Latest revision as of 15:28, 28 April 2009

ZCA

There is no ZCA in pyogp

Buildout

It is being considered whether we want to do away with buildout. Perhaps some day we shall, but it works, and there is no urgency.

Arguments

  1. Setting up path – we can use buildout to setup our path automatically for development. Without buildout, we would have to set the path ourselves, which would be difficult because of the dependencies and the relation to the system we are on.
  2. Setting up the environment – can use buildout to automatically fetch the dependencies we rely upon (downloading eggs, getting svn projects, etc)
Retrieved from "https://wiki.secondlife.com/w/index.php?title=Pyogp/Design_Decisions&oldid=338773"