[Repoze-dev] [issue118] chapter 4
New submission from Will Seaver will.sea...@gmail.com: my understanding of the WSGI protocol is that it converses between the application and the browser. is this correct? I am in need of definitions of API and application registry. p. 26: the code within the if block [from 4.1.3] should only be run during a direct script execution. What are the circumstances under which the script would not be directly executed? p. 32: Because ZCML is XML, and because XML request a single root tag for each document... meaning that the configure tab effectively signifies that this is an XML document? -- messages: 349 nosy: kwseaver priority: wish status: unread title: chapter 4 topic: bfg book __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue118 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue119] chapter 5
New submission from Will Seaver will.sea...@gmail.com: the paster template I am most familiar with is bfg_zodb, correct? that seemed to be the most accurate out of the ones listed. In general, the format of .ini files is pretty opaque to me, even after reading the chapter. How important is it that I obtain a working understanding of them? p. 39: That directory [MyProject] is a setuptools project directory from which a setuptools distribution can be created. A distribution as in a way to propagate the project to others? p. 39: This [../bin/python setup.py develop] will install the distribution representing your applications into the interpreter's library set so it can be found and run by PasteDeploy via the command paster serve This enables the application to talk to the server? p. 40: What exactly is the interactive shell? p. 42: ...you can run the application it represents using the paster serve command against the generated configuration file. In our case, this file is named MyProject.ini. Are both .ini and .zcml configuration files? This confused me. p. 43: Will it ever be necessary for me to use an alternate WSGI server? Definitions needed: wrapper (as in, p. 45: The MyProject project is the distribution and deployment wrapper for your application) PasteDeploy (p. 45: The MyProject.ini file is a PasteDeploy configuration file) middleware (p.46: ...global parameters that are shared by all the applications, servers and middleware) root factory (p. 53: Line 6 is a root factory function that will be called by the repoze.bfg Router...) A good working definition of what eggs are would also help me greatly. p. 53: run.py - this file does the same thing as can be done in imperatively-written view code? -- messages: 350 nosy: kwseaver priority: wish status: unread title: chapter 5 topic: bfg book __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue119 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue120] chapter 6
New submission from Will Seaver will.sea...@gmail.com: p. 57: In order for a web application to perform any useful action, the web framework must provide a mechanism to find and invoke code written by the application developer based on parameters present in the request. to rephrase: repoze.bfg must find a way to turn the request into application data. is this correct? p. 57: it [context finding subsystem] is responsible for finding a context object and a view name based on information present in the request. does it find these things inside the configure.zcml? p. 58: Essentially, URL-dispatch based systems just don't deal very well with URLs that represent arbitrary-depth hierarchies. I am unclear on what an arbitrary-depth hierarchy would be; an example would be helpful for my understanding. -- messages: 351 nosy: kwseaver priority: wish status: unread title: chapter 6 topic: bfg book __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue120 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue121] chapter 7
New submission from Will Seaver will.sea...@gmail.com: In general, this is where my big problems began. My understanding of the traversal algorithm was completely stymied by one thing: a lack of knowledge about the __getitem__ method. If I understood this one piece of the puzzle better, the whole thing would fall into place for me. I could glean some information without understanding __getitem__, but without that knowledge, I could not completely understand. With that out of the way, on to the line by line notes: The analogy given on p. 62 was very helpful toward what understanding I do have of traversal now. Thank you very much for that; it helped me to understand the brute force nature of the protocol much better. In the example url given on p. 62 (http://example.com:8080/a/b/c?foo=1, 'a' is the root object, 'b' is the view name and 'c' is the context, correct? p. 69: Let's say that view lookup finds no matching view type. In this circumstance, the repoze.bfg router returns the result of the not found view and the request ends. I did not understand this at the time, but later reading revealed the existence of the not_found view, and now I've got it. Definitions needed: object graph (p. 61: It [traversal] is the act of finding a context and a view name by walking over an object graph...) this has something to do with the models.py correct? container node and leaf node (p. 65: The object graph consists of container nodes and leaf nodes.) Container nodes have children and leaf nodes do not, yes? -- messages: 352 nosy: kwseaver priority: wish status: unread title: chapter 7 topic: bfg book __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue121 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] PyCon presentations...
Two BFG-related presentations from PyCon 2010 are now online: Carlos de la Guardia's Pay Only for What You Eat: A tour of the repoze.bfg repository and philosophy http://pycon.blip.tv/file/3263959/ Tres Seaver's Evolving Your Framework Under Fire http://pycon.blip.tv/file/3261349/ - C ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev