Jump to content

Talk:Solution stack

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 94.222.75.90 (talk) at 18:45, 4 January 2013 (FAPP: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconComputing Unassessed
WikiProject iconThis article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
???This article has not yet received a rating on Wikipedia's content assessment scale.
???This article has not yet received a rating on the project's importance scale.

LAMP isn't a very good example of a layered software system as the AMP are all co-planar.


a) Please sign your comments.
b) If you're not going to write your comments in English than I suggest you post your comments to the Jargon version of Wikipdia...oh wait, there isn't one of those. <grin>
c) Can someone please translate "co-planar" to an understandable form; pretty please.
--TMH (talk) 21:14, 1 March 2008 (UTC)[reply]

I imagine that by co-planar, the author of the comment above meant that these software "layers" aren't layered as such, in the sense that each exists "within" the next one. I'd disagree with respect to PHP running inside Apache, though (details like external fcgi processes aside).

I think the "stack" aspect refers more to conceptually visualising which software makes use of which products (which looks more like a dependency graph, to me). In other words, "stack" as used here does not mean literally running inside each layer.

Incidentally, the article says "a solution stack is a set of software subsystems". A stack (in the data structure sense) isn't a set; sets are unordered. This might be worth clarifying. Kate (talk) 15:37, 14 September 2008 (UTC)[reply]

The OP posted from Microsoft IP space. I don't know what they meant by "co-planar" in this content, as except possibly for LYME, the "AMP" aren't "co-planar" by any useful meaning I can construct for it. Andy Dingley (talk) 14:26, 25 September 2008 (UTC)[reply]

Better naming?

Any thoughts on better naming?

This article lists some broad options for low-level platforms (not even frameworks) from which to build dynamic web apps. "Solution stack" doesn't convey the web-app nature of this at all.

They are:

  • Web-based
  • Stacks, with ordered layers.
  • Ways of building "web applications", which is somewhat narrower than "solutions"

They're not:

  • Open source (all of them, or every layer)
  • Frameworks (in the additional sense that Ruby on Rails, CherryPy etc. are)

"List of ..." is also a possibility, according to local conventions (or is there too much detail for a mere list?)
"Comparison of ..." ?
Andy Dingley (talk) 14:30, 25 September 2008 (UTC)[reply]

This page is horrible

Really, all this page does is talk about LAMP. If I wasn't so lazy, I would nominate it for deletion. —Preceding unsigned comment added by 24.99.60.219 (talk) 22:44, 15 May 2011 (UTC)[reply]

It also seems somewhat out of date. Nginx is becoming a widely used alternative to Apache web server and this is not reflected in the page. --Ross Engers (talk) 13:47, 21 July 2012 (UTC)[reply]

I agree - it refers to a vague cheesy marketing term rather than anything valuable to someone interested in the subject. Better information is already available on other pages. 76.168.83.54 (talk) —Preceding undated comment added 07:43, 3 August 2012 (UTC)[reply]

FAPP

Free BSD, Apache, Postgre, Perl