good! let's iterate then --- bottom-up; top-down; we'll form better ideas
about if this is good by trying...
On Thu, May 21, 2009 at 5:33 PM, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> I have implemented this (and I will post it in trunk tonight) and you
> can be assured that it does not affect static files. They are treated
> in a different way than dynamic files. Of course it is also backward
> compatible.
>
> What I am not sure is whether it is a good idea to have customizable
>
> views/generic.html
> views/generic.xml
> views/generic.json
> views/generic.rss
> views/generic.yaml
> views/generic.pickle
> ...
>
> or if these functions should be hardcoded in web2py.
>
> Massimo
>
>
>
>
> On May 21, 4:16 pm, JohnMc <maruadventu...@gmail.com> wrote:
> > Well no, of course.
> >
> > As a general rule, I place relevant static pages under /static/
> > subfolder/the_file_name.html in many cases. Even if it is another web
> > server accessing the files. I utilize the packaging that web2py
> > provides to facilitate moves when a application needs to be relocated.
> >
> > It might be bad practice but while others are running down errors the
> > Web2Py app is already running. I would hate to lose that facility.
> >
> > On May 21, 3:30 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
> >
> > > This will not create any conflict, unless you have files with
> > > extensions other than .html in the views folder (and you should not).
> >
> > > Massimo
> >
> > > On May 21, 2:55 pm, JohnMc <maruadventu...@gmail.com> wrote:
> >
> > > > Yarko,
> >
> > > > I should explain. In some instances when I put together the view I
> > > > will have code segments that are pulled in as a {{include}}. No
> > > > controller involved at all. Having to do the controller call would
> not
> > > > be such a hassle of course. But in a site where much of the content
> is
> > > > static html and web2py is used to handle some dynamic components it
> > > > seems a waste to now have to have the content flow through web2py
> > > > first.
> >
> > > > If you tell a site owner in such an instance that he has to have
> > > > controller pass thru for all his legacy content he will look
> > > > elsewhere.
> >
> > > > On May 21, 2:41 pm, JohnMc <maruadventu...@gmail.com> wrote:
> >
> > > > > these should be under controller name "static", so I don't expect
> what
> > > > > Massimo describes will conflict. -- Yarko
> >
> > > > > Even if they are an {{include}} in the view?
> >
> > > > > On May 21, 11:50 am, Yarko Tymciurak <yark...@gmail.com> wrote:
> >
> > > > > > these should be under controller name "static", so I don't expect
> what
> > > > > > Massimo describes will conflict.
> > > > > > But this brings up another intersting glitch we've had - static
> files that
> > > > > > refer in their own links to a directory making the long-standing
> assumption
> > > > > > that any server will "look for" index.html in the directory if no
> file is
> > > > > > specified. Microsoft's IIS servers do more: they setup a "path"
> of default
> > > > > > files, and allow you to add and re-order that list, e.g.
> "default.asp;
> > > > > > default.html; index.html" --- which is nice, because it is
> general.
> >
> > > > > > For example, when trying to "implement" sqldesigner, it's help
> files could
> > > > > > not be used in web2py because of this lack of "looking for static
> files, if
> > > > > > path turned out to be just a directory".
> >
> > > > > > While, from a code perspective, this is a separate issue - from a
> logical
> > > > > > perspective, it is a related feature - doing something
> historically normal
> > > > > > with paths.
> >
> > > > > > On Thu, May 21, 2009 at 11:42 AM, JohnMc <
> maruadventu...@gmail.com> wrote:
> >
> > > > > > > Any conflict with static files that might be called from within
> a view
> > > > > > > of the same name. (html specifically.)
> >
> > > > > > > On May 21, 10:48 am, mdipierro <mdipie...@cs.depaul.edu>
> wrote:
> > > > > > > > I am talking a small change to the current web2py (10 lines)
> and I can
> > > > > > > > do it tonight if no objection. It would help users build more
> restful
> > > > > > > > apps although it does not have to be stateless.
> >
> > > > > > > > Massimo
> >
> > > > > > > > On May 21, 10:37 am, DenesL <denes1...@yahoo.ca> wrote:
> >
> > > > > > > > > As part of an architected move towards RESTful web
> services, or would
> > > > > > > > > that be in web2py v2? ;-)
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
