You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Per Steffensen <st...@designware.dk> on 2001/05/21 14:33:21 UTC
Research
Hi
Im writing my master theisis in computer science, on topics as the ones listed below. I want to ask you if you know of any "related work" - in the sence that it contains topics simular or close to one or more of the listed topics. Or maby you know of other places to ask or start my research. Any input will be apprechiated - please give me all you've got. I will sort the material. Cocoon itself is f.ex related work, cause it contains topics related to the ones listed (in the bottom of this mail I explain what I mean by some of the more central and ambiguous words).
- Description of a service in a platform-neutral (not HTML, WML or anything specific for a platform) language. Interpretation/styling of such service so that it will end up working on misc platforms (WEB, WAP, Imode etc)
- More nodes of a graph-based service put in the same file. E.g on web services each node is in its own file - you do not have two or more nodes in the same file. Ofcause in such a service the service engine should remove non-current nodes from the full file, before handing it over to the client.
- Fixed structure of a graph-based service. That is - you can ONLY navigate along the defined edges - you CANNOT navigate freely to any node you like, like you f.ex can on the web.
- Again for graph-based services. Connection information about the content of a node to the different edges pointing to it. That is - parts can be added to a node depending on, along wich edge you arrived at the node. This way a node can e.g dynamicly change parts of its content depending on wich node you came from.
- An enviroment connected to each user of the service, in wich the service-programmer can store infomation. Especially interesting if the system supports setting back the state of the enviroment, if the user backtraps (e.g a parallel to pushing the "back" button of a web-browser) in his use of the service.
- Service engines that checks the format of user-input, according to format-rules (e.g regular expressions) set up by the service-programmer.
- Allowing the USER to decide the styling of the responces he gets from the service engine. In Cocoons XSL the styling is decided by the PROGRAMMER and not he user.
- Service engines that support setting up database tables, control its fields, inserting/deleting records on startup of the engine.
Vocabulary:
- service: A "place" here clients can get to, to get served in some way (get some information, give way some information etc. Most web-sites can be regarded as a service)
- graph-based service: Is a service where the user gets the impression that he is moving around between nodes (subparts of the service) along edges (links in the service). As an example the web offers graph-based services, where the html-pages is nodes and the links between them is edges.
- enviroment: A "place" to store information. E.g a 1-1 relation between variable-name and -value.
Thanx
Per Steffensen