My 2c worth.
I am by no means a Mickysoft lover but.....
Last year I developed a windows DNA solution based on principes not dislike
that of peer model. We had very little on the ASP side and bundled our
code/logic in DLL's for easy reusability & maintainability spread over six
machines incorporating 3 layers. I have to say it worked great.
Having said that I hate being tied into specific OS's (windoos) and not
being able to see the source code of the API's I'm using.
I would say that Turbine pushes you more in the MVC model way due to the
manner in which it works as an API. Otherwise if one was to work with JSP &
JAVA the same problem as you describe below would occur.
/Colin
> From: "Jeb Boniakowski" <[EMAIL PROTECTED]>
> > The company I work for has done a lot of stuff with ASP and they want to
use
> > Java based technologies for all projects moving forward. One of the
reasons
> > is that they feel that their ASP code (which I've never worked on or
seen)
> > is completely unmaintainable and is write-only. New developers have a
> > really hard time understanding it, and it's hard not to replicate code
> > through many pages, making changes to that code really annoying. I
don't
> > know much about ASP, but this is something my boss told me about their
ASP
> > projects.
> >
> > jeb.
>
> I'd have to agree with the comments from Jeb's boss. Apart from the
obvious
> lack of portability ASP does indeed tend to be really messy and
unmaintainable.
> I have seen an ASP site that was written in a very structured manner and
it
> was reasonably maintainable, but this is certainly not typical and in any
case the
> example was not overly complex.
>
> The whole MVC argument has surely got to be your strongest argument. With
ASP
> you are stuck with the presentation and the logic in one messy lump.
Turbine,
> particularly when using the pull method is a really nice way out of this
mess.
> Of course with Turbine you also get a whole bunch of useful services that
would
> otherwise be a real challenge to assemble.
>
> With Java based solutions you get all the niceties of OO based languages
along
> with other benefits such as great deployment options (I've never seen an
ASP
> app deploy as nicely as a war file).
>
> You mentioned the web designer's use of applets. These are going to be
more
> difficult in the future as M$ are not going to include a JVM at all in
WinXP.
>
> Don't forget that M$ is also throwing away ASP for ASP+ - I can't claim
> any particular knowledge, but it seems that ASP+ is more along the lines
> of JSP whereby you end up with compiled code.
>
> From a learning and productivity perspective, Turbine wins hands down
> over ASP.
>
> Just some random thoughts. Hope they help.
>
> BTW: I'm throwing away my ASP application and rewriting it using Turbine.
>
> Scott
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
