Software requirements - Revision history

Jukeboksi: + Category:Technology

2021-04-12T19:24:45Z

← Older revision		Revision as of 19:24, 12 April 2021
Line 8:		Line 8:
	*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be?		*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be?
	*[[PHP]] - useful tool or slow script-kiddie fluff?		*[[PHP]] - useful tool or slow script-kiddie fluff?

			[[Category:Technology]]

Jukeboksi: :Text is the default still

2004-03-10T12:32:16Z

:Text is the default still

← Older revision		Revision as of 12:32, 10 March 2004
Line 4:		Line 4:

	*[[audio]] vs. [[video]] as primary presentation of [[Consumerium buying signal]]		*[[audio]] vs. [[video]] as primary presentation of [[Consumerium buying signal]]
			:Text is the default still
	*[[Python]] vs. [[Java]] - consider [[mobile device]] and [[wiki code]] issues		*[[Python]] vs. [[Java]] - consider [[mobile device]] and [[wiki code]] issues
	*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be?		*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be?
	*[[PHP]] - useful tool or slow script-kiddie fluff?		*[[PHP]] - useful tool or slow script-kiddie fluff?

142.177.76.153 at 04:52, 10 March 2004

2004-03-10T04:52:43Z

← Older revision		Revision as of 04:52, 10 March 2004
Line 1:		Line 1:
	'''Software requirements''' are so constrained by [[hardware requirements]] and [[~~protocol~~ requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]].		'''Software requirements''' are so constrained by [[hardware requirements]], [[protocol requirements]] and (especially) [[performance requirements]] that we should avoid choosing any [[programming language]], production [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]] and its low tolerance for [[e-waste]] or [[volunteer labour]].

	Some questions to keep in mind as these concepts evolve:		Some questions to keep in mind as these concepts evolve:

142.177.76.153 at 04:27, 10 March 2004

2004-03-10T04:27:40Z

← Older revision		Revision as of 04:27, 10 March 2004
Line 4:		Line 4:

	*[[audio]] vs. [[video]] as primary presentation of [[Consumerium buying signal]]		*[[audio]] vs. [[video]] as primary presentation of [[Consumerium buying signal]]
	*[[Python]] vs. [[Java]]		*[[Python]] vs. [[Java]] - consider [[mobile device]] and [[wiki code]] issues
	*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be?		*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be?
			*[[PHP]] - useful tool or slow script-kiddie fluff?

142.177.76.153: questions

2004-03-10T04:26:56Z

questions

← Older revision		Revision as of 04:26, 10 March 2004
Line 1:		Line 1:
	'''Software requirements''' are so constrained by [[hardware requirements]] and [[protocol requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]].		'''Software requirements''' are so constrained by [[hardware requirements]] and [[protocol requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]].

			Some questions to keep in mind as these concepts evolve:

			*[[audio]] vs. [[video]] as primary presentation of [[Consumerium buying signal]]
			*[[Python]] vs. [[Java]]
			*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be?

142.177.97.132: typo

2003-11-22T00:02:24Z

typo

← Older revision		Revision as of 00:02, 22 November 2003
Line 1:		Line 1:
	'''Software requirements''' are so constrained by [[hardware requirements]] and [[protocol requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying ~~instrastructure~~]] is much better understood. This starts by understanding the [[healthy signal infrastructure]].		'''Software requirements''' are so constrained by [[hardware requirements]] and [[protocol requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]].

142.177.97.132 at 00:02, 22 November 2003

2003-11-22T00:02:07Z

New page

'''Software requirements''' are so constrained by [[hardware requirements]] and [[protocol requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying instrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]].