[SNG-CVS] sng-design features,1.10,1.11 globalorg.txt,1.1,1.2 subsystems.txt,1.1,1.2

[<ln...@us...>]

Update of /cvsroot/servicesng/sng-design
In directory sc8-pr-cvs1:/tmp/cvs-serv16301

Modified Files:
	features globalorg.txt subsystems.txt 
Log Message:
spell checked, ok, thats mainly for testing syncmail :)

Index: features
===================================================================
RCS file: /cvsroot/servicesng/sng-design/features,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** features	6 Jan 2003 09:54:07 -0000	1.10
--- features	7 Jan 2003 14:08:21 -0000	1.11
***************
*** 7,11 ****
  This list should mainly be used as a checklist while designing the services
  architecture, to make sure everything we want to be added one day could be done
! without rewritng everything.
  
  Furthermore, this list isn't a list of goals. Some of the modules listed above
--- 7,11 ----
  This list should mainly be used as a checklist while designing the services
  architecture, to make sure everything we want to be added one day could be done
! without rewriting everything.
  
  Furthermore, this list isn't a list of goals. Some of the modules listed above
***************
*** 19,23 ****
  
  - Handles for users, as explained by Simon Bell :
! "I dont know if this type of feature would be welcome or not, but quite a
  few of the users dont particularly like services which use nickname
  ownership. I would love to see an option where i could specify that the
--- 19,23 ----
  
  - Handles for users, as explained by Simon Bell :
! "I don't know if this type of feature would be welcome or not, but quite a
  few of the users dont particularly like services which use nickname
  ownership. I would love to see an option where i could specify that the
***************
*** 30,34 ****
  - Several ways to access services.
    - classic /nickserv, /chanserv, /memoserv, etc ...
!   - others ways, more userfriendly, which could include :
      - a global /services, designed to be more simple.
      - direct http access to the services for configuration purposes
--- 30,34 ----
  - Several ways to access services.
    - classic /nickserv, /chanserv, /memoserv, etc ...
!   - others ways, more user-friendly, which could include :
      - a global /services, designed to be more simple.
      - direct http access to the services for configuration purposes
***************
*** 65,69 ****
    - LogServ - A notepad service. It keeps a log on irc for quick notes,
      the log can then be emailed to the user, or posted on the web.
!   - AdServ - An advertising service. It manages and pases managed advertising
      messages to all users/chans.
    - VoteServ - A system to allow users in a channel list to create polls
--- 65,69 ----
    - LogServ - A notepad service. It keeps a log on irc for quick notes,
      the log can then be emailed to the user, or posted on the web.
!   - AdServ - An advertising service. It manages and passes managed advertising
      messages to all users/chans.
    - VoteServ - A system to allow users in a channel list to create polls

Index: globalorg.txt
===================================================================
RCS file: /cvsroot/servicesng/sng-design/globalorg.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** globalorg.txt	7 Jan 2003 13:34:13 -0000	1.1
--- globalorg.txt	7 Jan 2003 14:08:22 -0000	1.2
***************
*** 72,76 ****
    wouldn't be needed to be able to modify it externally (and there's no need
    for this neither).
! Also, Interface Modules can be Services Modules, and Services Modules can be Interface Modules. The seperation of the visible part and the background part is better, but for small services, or services where it is difficult to seperate those two parts, they could be merged.
  
  8. Database abstraction layers
--- 72,76 ----
    wouldn't be needed to be able to modify it externally (and there's no need
    for this neither).
! Also, Interface Modules can be Services Modules, and Services Modules can be Interface Modules. The separation of the visible part and the background part is better, but for small services, or services where it is difficult to split those two parts, they could be merged.
  
  8. Database abstraction layers

Index: subsystems.txt
===================================================================
RCS file: /cvsroot/servicesng/sng-design/subsystems.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** subsystems.txt	7 Jan 2003 13:34:13 -0000	1.1
--- subsystems.txt	7 Jan 2003 14:08:22 -0000	1.2
***************
*** 21,25 ****
  Priority : High
  Tasks : Design a small interface module, for testing purposes
! Requirements : speed and availiability : this need to be done soon.
  
  Subsystem : IRC
--- 21,25 ----
  Priority : High
  Tasks : Design a small interface module, for testing purposes
! Requirements : speed and availability : this need to be done soon.
  
  Subsystem : IRC