Class: NetworkRequest (in Comanche)

• Inheritance
• Description
• Class protocol
  • instance creation
• Instance protocol
  • accessing
  • initialize-release
  • properties
  • testing

Inheritance:

   Object
   |
   +--Comanche::NetworkRequest
      |
      +--Comanche::HttpRequest

Package:

stx:goodies/webServer/comanche/swiki

Category:

Comanche-Kom-Protocol-Abstract

Version:

rev: 1.10 date: 2003/09/11 12:48:12

user: cg

file: NetworkRequest.st directory: goodies/webServer/comanche/swiki

module: stx stc-classLibrary: swiki

Description:

Kom48 (Comanche beta 4.8)
bolot 4/2/2001 18:53

NetworkRequest
- a generic request object
- properties are some ad-hoc properties
- session is not currently used

Note about Kom46:
- this class contained more methods
-- some methods have been depricated since

Class protocol:

 new

(comment from inherited method)
return an instance of myself without indexed variables

Instance protocol:

 method

** This method must be redefined in concrete classes (subclassResponsibility) **

 session

 session: aSession

 url

** This method must be redefined in concrete classes (subclassResponsibility) **

 initialize

(comment from inherited method)
just to ignore initialize to objects which do not need it

 propertyAt: aSymbol

(comment from inherited method)
return the property for a given key or raise an error if not found.
Such propertys behave like dynamically addable slots in languages like JavaScript.
They are much more expensive though, because they are not a ''natural'' mechanism in Smalltalk,
but instead simulated via an additional properties collection mechanism, which
defaults to using a dictionary holding per instance properties.
So only use it for seldom needed/seldom assigned properties,
and only if it is not easy to add an instance variable or class-private mechanism for that.

Notice: properties and objectAttributes are similar mechanisms to dynamically add slots to an object.
Sigh: objectAttributes are older, and are named properties in Pharo.

 propertyAt: aSymbol ifAbsent: absentBlock

(comment from inherited method)
return the property for a given key or defaultValue if not present.
Such propertys behave like dynamically addable slots in languages like JavaScript.
They are much more expensive though, because they are not a ''natural'' mechanism in Smalltalk,
but instead simulated via an additional properties collection mechanism, which
defaults to using a dictionary holding per instance properties.
So only use it for seldom needed/seldom assigned properties,
and only if it is not easy to add an instance variable or class-private mechanism for that.

Notice: properties and objectAttributes are similar mechanisms to dynamically add slots to an object.
Sigh: objectAttributes are older, and are named properties in Pharo.

 propertyAt: aSymbol ifAbsentPut: absentBlock

(comment from inherited method)
return the property for a given key or the added defaultValue if not present.

Notice: properties and objectAttributes are similar mechanisms to dynamically add slots to an object.
Sigh: objectAttributes are older, and are named properties in Pharo.

 propertyAt: aSymbol put: anObject

(comment from inherited method)
store the property anObject referenced by key into the receiver.
Such propertys behave like dynamically addable slots in languages like JavaScript.
They are much more expensive though, because they are not a ''natural'' mechanism in Smalltalk,
but instead simulated via an additional properties collection mechanism, which
defaults to using a dictionary holding per instance properties.
So only use it for seldom needed/seldom assigned properties,
and only if it is not easy to add an instance variable or class-private mechanism for that.

Notice: properties and objectAttributes are similar mechanisms to dynamically add slots to an object.
Sigh: objectAttributes are older, and are named properties in Pharo.

 removePropertyAt: aSymbol

 removePropertyAt: aSymbol ifAbsent: aBlock

 isGetRequest

** This method must be redefined in concrete classes (subclassResponsibility) **

 isHeaderRequest

** This method must be redefined in concrete classes (subclassResponsibility) **

 isPostRequest

** This method must be redefined in concrete classes (subclassResponsibility) **