Re: D2W and Direct Actions
Re: D2W and Direct Actions
- Subject: Re: D2W and Direct Actions
- From: Guido Neitzer <email@hidden>
- Date: Fri, 1 Jun 2007 09:50:56 -0600
On 01.06.2007, at 01:02, Denis Frolov wrote:
I have one too and use it for Admin apps.
Yeah, makes sense not to re-invent the wheel too often ... ;-) One of
the problems I have with that, is that my "Admin" applications are
normally also user / customer accessed applications, so they have to
be polished to a certain degree and therefor I'm always happy when I
have really clean HTML and styles in that. That's one reason why I
subclassed nearly every non-trivial component from ERD2W to get in my
own HTML, my own classes with a naming convention for CSS styles,
much less tables, more div and span tags and more stuff configurable
by rules (like css classes taken from rules, page header's and titles
configured by rules, a lot of <h> tags configured by rules and so on).
All our "frontend" apps are bookmarkable. There is no reason you
cannot use direct actions with D2W.
I know that. But I don't like the fact, that so many sessions are
created when they are not needed. Might be an old fashioned thought
or from some bad experience with search engines.
can write your own direct actions. D2W combined with direct actions
can be effectively used to create list, inspect, edit, etc pages.
I know that. I use that a lot in development to come to a page fast.
Never considered using it in a "portal" area though. Might give that
a thought in the next weeks.
Consider an example (we don't own the project, so I hope you won't
consider this an advertisement): http://www.legalsounds.com/
InspectArtist?__key=3339
The application is really impressive from the point, that it hides
its technology VERY well. But who was killed for the HTML? ;-)
On the first glance I have two questions: how well does the
application handle search engines? I saw that you're storing session
ids in cookies to get the bookmarkable urls in combination with
DirectActions. We had some trouble years ago with search engines not
taking the cookie and flooding the application with sessions (like
over 200 Sessions created per minute, the app went down with about
3000 sessions spread over four instances).
And the second question: how did you do the URL creation? I'm still
looking for a good way of creating "nice" URLs. I'm absolutely no
Apache specialist, I know it's the WebServer used on Mac OS X
Server ... okay, no kidding, I know a bit but not nearly enough. Over
the time I saw a couple of interesting approaches for nicer URLs but
I haven't decided to use one of them for my own apps ...
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden