On Thu, 23 Aug 2007, David Lyon wrote:
> Michael Van Canneyt wrote:
> > In these structures it's faster to have the form per session in
> > memory (stateful), so what you call the 'native model'.
> > It's also much easier and intuitive to program.
> >
> The problem with using the form paradigm with the web paradigm is that there
> is usually only one form at a time on the client browser (unless multiple
> tabs) and it is frequently being rebuilt (from objects) and re-issued.
>
> With the "object-publishing-model" that I've been reading about, it is
> entirely different, and if anything much simpler conceptually.
>
> Translating to pascal, there is a session object, which links to a
> TCollection...
>
> In that TCollection are all the objects (components) of the page, like the
> header, logo, navigation pane, content pane, portal pane and body pane.
>
> Each object (component) can "render" itself when asked.
>
> When the user clicks a button that might cause the body text to change, the
> change is made to the body object and all the objects in the TCollection are
> asked to re-render.
>
> That output is then sent out to the browser which displays it all again.
>
> I definitely have not seen this approach being used in pascal web serving so
> far. It is being used in python and the results are supurb.
But it is what Intraweb does. Change the TCollection with a TForm, and that's
it.
Where is the difference ?
Michael.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
