| Programming Systems Laboratory. Application Specific Http Services (ASHeS). www.psl.cs.columbia.edu/software/ashes.html. |
....and clients, but also between peer tool servers. HTTP (as opposed to, say, RPC or CORBA) was selected because it is a simple TCP IP based request response protocol, making it easy to graft onto existing systems (possibly using toolkits like libWWW [16] from the World Wide Web Consortium or ASHeS [47], the Application Specific HTTP Services toolkit from our research group) The HTTP specification provides methods for a client to request a document (HTTP GET) and send data (HTTP PUT) to a server. In our architecture, the URL is treated as a request for a tool. Users connect to tool servers via ....
Programming Systems Laboratory. Application Specific Http Services (ASHeS). www.psl.cs.columbia.edu/software/ashes.html.
....method not only between clients and servers, but between peer tool servers as well. HTTP is chosen because it is a simple TCP IP based request response protocol, making it easy to graft onto existing systems (possibly using toolkits like libWWW [6] from the World Wide Web Consortium or ASHeS [12], the Application Specific HTTP Services toolkit from our research group) The HTTP specification provides methods for a client to request a document (GET) and send data (PUT) to a server. The documents are specified by URLs (Uniform Resource Locators [2] which are really just strings that ....
Programming Systems Laboratory. Application Specific Http Services (ASHeS). http://www.psl.cs.columbia.edu/software/ashes.html.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC