]> BibSonomy publications for /author/Frystyk http://www.bibsonomy.org/burst/author/Frystyk BibSonomy BuRST Feed for /author/Frystyk 2008-07-20T23:35:05+02:00 High Performance Multi-paradigm Messaging Runtime Integrating Grids and Multicore Systems. dblphttp://www.bibsonomy.org/bibtex/243e677eb0da2721a7c9136a87d671c30/dblp dblp 2008-07-14T00:00:00+02:00 dblp
High Performance Multi-paradigm Messaging Runtime Integrating Grids and Multicore Systems.
Xiaohong Qiu and Geoffrey Fox and Huapeng Yuan and Seung-Hee Bae and George Chrysanthakopoulos and Henrik Frystyk Nielsen eScience 407-414 (2007)
to dblp by dblp on 2008-07-14 00:00:00 ]]> eScienceconf/eScience/2007407-414High Performance Multi-paradigm Messaging Runtime Integrating Grids and Multicore Systems.2007dblp 2008-07-14 00:00:00.0 Performance of Multicore Systems on Parallel Data Clustering with Deterministic Annealing. dblphttp://www.bibsonomy.org/bibtex/25b77e7b5fc7c3ebf60e0691625a7133a/dblp dblp 2008-06-30T00:00:00+02:00 dblp
Performance of Multicore Systems on Parallel Data Clustering with Deterministic Annealing.
Xiaohong Qiu and Geoffrey Fox and Huapeng Yuan and Seung-Hee Bae and George Chrysanthakopoulos and Henrik Frystyk Nielsen ICCS (1) 407-416 (2008)
to dblp by dblp on 2008-06-30 00:00:00 ]]> ICCS (1)conf/iccS/2008-1407-416Lecture Notes in Computer SciencePerformance of Multicore Systems on Parallel Data Clustering with Deterministic Annealing.51012008dblp 2008-06-30 00:00:00.0 Hypertext Transfer Protocol -- HTTP/1.1 http://www.bibsonomy.org/bibtex/2ce763037bc84d85b0773e0ccefc977f4/vrandezo vrandezo 2008-04-02T15:35:07+02:00 imported
Hypertext Transfer Protocol -- HTTP/1.1
Roy Fielding and James Gettys and Jeffrey Mogul and Henrik Frystyk and Larry Masinter and Paul Leach and Tim Berners-Lee (1999)
to imported by vrandezo on 2008-04-02 15:35:07 ]]> RFC 2616June2616Request for Comments{Hypertext Transfer Protocol -- HTTP/1.1}1999imported 2008-04-02 15:35:07.0 Hypertext Transfer Protocol -- HTTP/1.1 http://www.bibsonomy.org/bibtex/2c97408d8a9b5e03b9e94d6c1ad123e00/seebi seebi 2008-01-04T18:19:06+01:00 jabref:noKeywordAssigned
Hypertext Transfer Protocol -- HTTP/1.1
R. Fielding and J. Gettys and J. Mogul and H. Frystyk and L. Masinter and P. Leach and T. Berners-Lee (1999)
to jabref:noKeywordAssigned by seebi on 2008-01-04 18:19:06 ]]> #jun#http://www.ietf.org/rfc/rfc2616.txt2616Hypertext {T}ransfer {P}rotocol -- {HTTP}/1.1#rfc#1999jabref:noKeywordAssigned 2008-01-04 18:19:06.0The {H}ypertext {T}ransfer {P}rotocol ({HTTP}) is an application-level protocol for distributed, collaborative, hypermedia information systems. {I}t is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers [47]. {A} feature of {HTTP} is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. {HTTP} has been in use by the {W}orld-{W}ide {W}eb global information initiative since 1990. {T}his specification defines the protocol referred to as "{HTTP}/1.1", and is an update to {RFC} 2068 [33]. Hypertext Transfer Protocol - HTTP/1.1 Main paper DBhttp://www.bibsonomy.org/bibtex/2506e757144a50a28ed58ea4bb6817fd8/cameron cameron 2007-12-07T21:41:23+01:00 crawling
Hypertext Transfer Protocol - HTTP/1.1
R. Fielding and J. Gettys and J. Mogul and H. Frystyk and L. Masinter and P. Leach and T. Berners-Lee (1999)
to crawling by cameron on 2007-12-07 21:41:23 ]]> Hypertext Transfer Protocol - HTTP/1.11999crawling 2007-12-07 21:41:23.0 Simple Object Access Protocol (SOAP) 1.1 http://www.bibsonomy.org/bibtex/2c46df2147acb291df0020ae097b0e3ad/neilernst neilernst 2007-06-20T06:28:04+02:00 soap specification
Simple Object Access Protocol (SOAP) 1.1
Don Box and David Ehnebuske and Gopal Kakivaya and Andrew Layman and Noah Mendelsohn and Henrik Frystyk Nielsen and Satish Thatte and Dave Winer (2000)
to soap specification by neilernst on 2007-06-20 06:28:04 ]]> MayNOTE-SOAP-20000508Simple Object Access Protocol ({SOAP}) 1.1W3C Note2000soap specification 2007-06-20 06:28:04.0SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework. Hypertext Transfer Protocol -- HTTP/1.0 http://www.bibsonomy.org/bibtex/22d22a19d0e95290c912ca7001d25201e/neilernst neilernst 2007-06-19T18:34:53+02:00 http standard
Hypertext Transfer Protocol -- HTTP/1.0
T. Berners-Lee and R. Fielding and H. Frystyk (1996)
to http standard by neilernst on 2007-06-19 18:34:53 ]]> MayRFC1945Hypertext Transfer Protocol -- HTTP/1.0Informational memo1996http standard 2007-06-19 18:34:53.0 The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. It is a generic, stateless, object-oriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods (commands). A feature of HTTP is the typing of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification reflects common usage of the protocol referred to as "HTTP/1.0". Editing the Web: Detecting the Lost Update Problem Using Unreserved Checkout My Master Thesis bibliographyhttp://www.bibsonomy.org/bibtex/2fc90e7dac753e89cea70a6535b7e6cd0/yeah yeah 2007-05-29T15:45:23+02:00 imported
Editing the Web: Detecting the Lost Update Problem Using Unreserved Checkout
Henrik {Frystyk Nielsen} and Daniel LaLiberte (1999)
to imported by yeah on 2007-05-29 15:45:23 ]]> World Wide Web Consortium NoteMayEditing the Web: Detecting the Lost Update Problem Using Unreserved Checkout1999imported 2007-05-29 15:45:23.0Avoiding the lost update problem has been a notorious challenge when editing documents remotely on the Web using HTTP/1.0. While WebDAV provides an extended set of services for editing the Web, HTTP/1.1 provides a minimal set of hooks for avoiding the lost problem by detecting when versions have changed so that changes aren't lost in the editing process. While simple, these hooks are fundamental to editing the Web using HTTP/1.1 and are needed in Webdav as well. This Note explains a) how to use HTTP/1.1 to detect the lost update problem using preconditions and strong etags and b) how to avoid problems with HTTP/1.0 clients that do not know about these features but only use plain HTTP PUT requests. Neither a) nor b) requires any changes to HTTP/1.1, but can be achieved using existing features. The mechanism has been implemented in Web Commander and Amaya (both using libwww), and Jigsaw --- all W3C Open Source software freely available to all interested parties. Detection is only one of several ways to avoid the lost update problem and this document discusses the pros and cons of various other mechanisms including exclusive locks and immutable revisions. Hypertext Transfer Protocol -- HTTP/1.1 My Master Thesis bibliographyhttp://www.bibsonomy.org/bibtex/2c97408d8a9b5e03b9e94d6c1ad123e00/yeah yeah 2007-05-29T15:45:23+02:00 imported
Hypertext Transfer Protocol -- HTTP/1.1
R. Fielding and J. Gettys and J. Mogul and H. Frystyk and L. Masinter and P. Leach and T. Berners-Lee 176 (1999)
to imported by yeah on 2007-05-29 15:45:23 ]]> June2616176Hypertext Transfer Protocol {--} {HTTP/1.1}RFC1999imported 2007-05-29 15:45:23.0The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. Hypertext Transfer Protocol -- HTTP/1.1 Hypertext Transfer Protocol - HTTP/1.1 - Fielding, Gettys, Mogul, Frystyk, Masinter, Leach, Berners-Lee (ResearchIndex)http://www.bibsonomy.org/bibtex/241a12b8e0073e2aff6f25a20ed9c7bb9/tmalsburg tmalsburg 2007-03-21T15:58:04+01:00 networking protocol specification
Hypertext Transfer Protocol -- HTTP/1.1
R. Fielding and J. Gettys and J. C. Mogul and H. Frystyk and L. Masinter and P. Leach and T. Berners-Lee (1998)
to networking protocol specification by tmalsburg on 2007-03-21 15:58:04 ]]> {Hypertext Transfer Protocol -- {HTTP}/1.1}1998networking protocol specification 2007-03-21 15:58:04.0