Notification servers for synchronous groupware

Patterson, John; Day, Mark; Kucan, Jakov

doi:10.1145/240080.240232

Cited by 72 publications

(38 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In its basic ideas, AMICO is similar to other loosely coupled and notification architectures such as Elvin [20], Lotus PlaceHolder, which is based on the Notification Service Transfer Protocol [44], and tuplespace systems, such as Linda [24], Stanford EventHeap [30], and JavaSpaces [18].…”

Section: Coordination Media: Amico Service Brokering Infrastructurementioning

confidence: 99%

End-User Service Computing: Spreadsheets as a Service Composition Tool

Obrenović

Gašević

2008

IEEE Trans. Serv. Comput.

View full text Add to dashboard Cite

Abstract-In this paper, we show how spreadsheets, an end-user development paradigm proven to be highly productive and simple to learn and use, can be used for complex service compositions. We identify the requirements for spreadsheet-based service composition and present our framework that implements these requirements. Our framework enables spreadsheets to send requests and retrieve results from various local and remote services. We show how our tools support different composition patterns and how the style of declarative dependencies of spreadsheets can facilitate service composition. We also discuss novel issues identified by using the framework in several projects and education.Index Terms-Online information services end-user development and service-oriented computing, information systems applications office automation and spreadsheets, software engineering distribution, maintenance, and enhancement.

show abstract

Section: Coordination Media: Amico Service Brokering Infrastructurementioning

confidence: 99%

End-User Service Computing: Spreadsheets as a Service Composition Tool

Obrenović

Gašević

2008

IEEE Trans. Serv. Comput.

View full text Add to dashboard Cite

show abstract

“…Rendezvous (Hill et al, 1994), Suite (Dewan and Choudhary, 1992), and Notification Service Transfer Protocol (NSTP) (Patterson et al, 1996) are sample groupware platforms, which use a central distribution scheme for the data of a collaborative application. A lot of groupware platforms, e.g., GroupKit (Roseman and Greenberg, 1996), COAST (Schuckmann et al, 1996), or DECAF (Strom et al, 1998) use the replicated distribution scheme.…”

Section: Related Workmentioning

confidence: 99%

Customizable Data Distribution for Synchronous Groupware

Lukosch

2004

Proceedings of the 4th International Workshop on Pattern Recognition in Information Systems

View full text Add to dashboard Cite

Abstract:The state of a groupware application must be shared to support interactions between collaborating users. There have been a lot of discussions about the best distribution scheme for the state of a groupware application. Many existing groupware platforms support only one distribution scheme, e.g. a replicated or a central scheme, and apply the selected scheme to the entire application. None of these schemes fits well for every groupware application. Different applications and even single applications have different requirements concerning data distribution. This paper describes DreamObjects, a development platform that simplifies the development of shared data objects. DreamObjects supports a variety of distribution schemes which can be applied per shared data object. Additionally, it offers an interface that developers can use to introduce their own distribution schemes.

show abstract

“…After the first proxy makes a particular request, the server may pre-send the result to other proxies in anticipation of their requests, accelerating the response to their request [17], [25]. When a replica leaves normally, the proxy notifies the server which discontinues tracking that replica's requests.…”

Section: ) Full Externality Replicationmentioning

confidence: 99%

Resource sharing for replicated synchronous groupware

Begole

Smith

Struble

et al. 2001

IEEE/ACM Trans. Networking

View full text Add to dashboard Cite

Abstract-We describe problems associated with accessing data resources external to the application, which we term externalities, in replicated synchronous collaborative applications. Accessing externalities such as files, databases, network connections, environment variables, and the system clock is not as straightforward in replicated collaborative software as in single-user applications or centralized collaborative systems. We describe ad hoc solutions that add to development cost and complexity because the developer must program different behavior for different replicas.We introduce a novel general approach to accessing externalities uniformly in a replicated collaborative system. The approach uses a semireplicated architecture where the actual externality resides at a single location and is accessed via replicated proxies. This approach allows developers of replicated synchronous groupware to 1) use similar externality access mechanisms as in traditional single-user applications, and 2) program all replicas to execute the same behavior. We describe a general design for proxied access to read-only, write-only, and read-write externalities and discuss the tradeoffs of this semireplicated approach over full, literal replication and the class of applications to which this approach can be successfully applied. We also describe details of a prototype implementation of this approach within a replicated collaboration-transparency system, called Flexible JAMM (Java Applets Made Multiuser).

show abstract

Notification servers for synchronous groupware

Cited by 72 publications

References 6 publications

End-User Service Computing: Spreadsheets as a Service Composition Tool

End-User Service Computing: Spreadsheets as a Service Composition Tool

Customizable Data Distribution for Synchronous Groupware

Resource sharing for replicated synchronous groupware

Contact Info

Product

Resources

About