Re: More fuel for the 64-bit fire ...
- From: "Craig Stuntz [TeamB]" <craig_stuntz@xxxxxxxxxxxxx [a.k.a. acm.org]>
- Date: 27 Jul 2005 05:10:33 -0700
Matt Jacobs wrote:
> Application servers have similar issues.
There are a couple of ways to read this statement. One would interpret
"application servers" as stuff like J2EE and JBoss. In this case I'd
agree, but developing such a system is hardly a routine task even
outside the warm fuzzy Delphi world. It's much like the DB world in
that the number of folks who use DB servers is exponentially larger
than the number of people who develop them. Your statement strongly
implied that non-Delphi developers implement SQL Server 2005-style
memory management much more routinely, so I guess you were talking
about something else.
The other way to read this would be stuff which runs *on* a system
like J2EE, which, confusingly, are commonly also called "application
servers." It's *much* more common to develop the latter than the
former, but even folks who don't use Delphi don't tend to do OS-level
memory management in this case. For lack of a better term I'll call
these "application server applications" to distinguish them from the
former, but this isn't standard terminology.
Most app server applications rely on OS or Java hardware services
rather than implement operating system-level memory management in lieu
of what Windows offers. Even those which implement their own memory
managers typically do it on top of OS services, not in lieu of them.
But, hey, I'm just a Delphi developer (well, not really, but...) and I
haven't seen everything in the world, so what do I know? I've already
supplied a link with details on how SQL Server 2005 handles memory at a
very low level elsewhere in this thread (without even mentioning .NET,
you'll be pleased to know). Folks who want to know more can and should
read the technical papers from Microsoft Research. I particularly like
Jim Gray's DB work.
So if non-Delphi app server application developers routinely do
similar things then it should be quite simple for you to come up with a
number of examples of correspondingly low level and yet extensible
memory management.
But I don't think you will.
--
Craig Stuntz [TeamB] . Vertex Systems Corp. . Columbus, OH
Delphi/InterBase Weblog : http://blogs.teamb.com/craigstuntz
Useful articles about InterBase development:
http://blogs.teamb.com/craigstuntz/category/21.aspx
.
- References:
- More fuel for the 64-bit fire ...
- From: Mat Ballard
- Re: More fuel for the 64-bit fire ...
- From: Rudy Velthuis [TeamB]
- Re: More fuel for the 64-bit fire ...
- From: Dallas Goldswain
- Re: More fuel for the 64-bit fire ...
- From: a
- Re: More fuel for the 64-bit fire ...
- From: Eric Grange
- Re: More fuel for the 64-bit fire ...
- From: Rudy Velthuis [TeamB]
- Re: More fuel for the 64-bit fire ...
- From: Eric Grange
- Re: More fuel for the 64-bit fire ...
- From: Mike Swaim
- Re: More fuel for the 64-bit fire ...
- From: Matt Jacobs
- Re: More fuel for the 64-bit fire ...
- From: Craig Stuntz [TeamB]
- Re: More fuel for the 64-bit fire ...
- From: Matt Jacobs
- More fuel for the 64-bit fire ...
- Prev by Date: Re: Guidelines please
- Next by Date: Re: Delphi 2005 and D7 code completion slow
- Previous by thread: Re: More fuel for the 64-bit fire ...
- Next by thread: Re: More fuel for the 64-bit fire ...
- Index(es):
Relevant Pages
|