as long as the resource loader asks for /app/static/something.js there is no absolute problem. AMD if used to load js files works his magic completely on client-side (vodoo-magic is requesting 5 js scripts at the same time without waiting and organize the evaluation in the right order).
>From the server standpoint, they are 5 totally normal requests coming for 5 resources, as if they were images in a blog. On Tuesday, December 18, 2012 12:12:24 AM UTC+1, Arnon Marcus wrote: > > I know it does for direct script-tag requests and also for that > web2py-python-api-usage done in the layout.html/ajax_whatever.html > thing... > > I mean how would a javascript-based loader do that? > I'm not that well versed in requier.js, but from what I read, the "A" in > AMD stands for asynchronous, so my guess is that the javascript in the > loader-library does some ajax-voodo or somethin... What is the > base-folder it requests? I mean, is web2py's ajax file-requests work fine > with this? Or do I have to do something special? Because I did have some > issues, for example with the "kickstrap" stack.that I suspected had > something or other to do with a custom javascript loader... > > On Monday, December 17, 2012 1:59:20 PM UTC-8, Niphlod wrote: >> >> every request done to /app/static/file.something is automatically served >> by web2py (matching a file into applications/app/static/file.something). >> >> >> On Monday, December 17, 2012 2:55:19 PM UTC+1, Arnon Marcus wrote: >>> >>> Another general issue regarding that: >>> >>> How would web2py behave using various modular javascript loaders? >>> Do I HAVE to configure my web server so serve the static folder? >>> How about AMD solutions (such as require.js and r.js), how would they >>> behave? >>> Is there a way to rout those requests through web2py? >>> Can the request be dependecy-calculated in the client-side, and >>> accumulated into a single request? >>> What are the proes/cons of doing that through web2py and/or through the >>> web server directly? >>> >> --
