Search (59 results, page 2 of 3)

0.0023678814 = product of:
  0.0047357627 = sum of:
    0.0047357627 = product of:
      0.009471525 = sum of:
        0.009471525 = weight(_text_:a in 7942) [ClassicSimilarity], result of:
          0.009471525 = score(doc=7942,freq=8.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.17835285 = fieldWeight in 7942, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=7942)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Describes types of international gateways available for online searching. Public data networks are provided by national telecommunications authorities. Private data networks are run by an organization for its own use, or for customers of its services. Academic data networks are a special case of private networks which serve the the academic and research communications. Gives details of a number of academic networks: JANET, BITNET, NETNORTH, EARN, Internet. Describes the gateways between JANET and the UK public data network, EARN and Internet. Describes the international X.25 infrastructure (IXI) network which is organized by COSINE (Cooperation for OSI networking in Europe) programme which aims to provide OSI-based services for European researchers

Source

Standards for the international exchange of bibliographic information: papers presented at a course held at the School of Library, Archive and Information Studies, University College, London, 3-18 August 1990. Ed.: I.C. McIlwaine

Type

a

0.0023678814 = product of:
  0.0047357627 = sum of:
    0.0047357627 = product of:
      0.009471525 = sum of:
        0.009471525 = weight(_text_:a in 8023) [ClassicSimilarity], result of:
          0.009471525 = score(doc=8023,freq=2.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.17835285 = fieldWeight in 8023, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.109375 = fieldNorm(doc=8023)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0023678814 = product of:
  0.0047357627 = sum of:
    0.0047357627 = product of:
      0.009471525 = sum of:
        0.009471525 = weight(_text_:a in 1176) [ClassicSimilarity], result of:
          0.009471525 = score(doc=1176,freq=8.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.17835285 = fieldWeight in 1176, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1176)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The ANSI Z39.50 standard was adopted 10 years ago. It outlines a set of rules and procedures to allow a computer system to search the databases provided by another system and to retrieve the results of that search. Traces its development adoption in library automation product lines. Recent major developments have been the migration to version 3 and the adoption of community profiles. Community profiles are documents that describe agreements that a community of interest develops to ensure clients and servers can interpret in specific ways. Describes the Government Information Locators Service, WAIS, ATS, ZDSR, Cataloguing, CEOS CIP, Digital Collection, Digital Library Objects and Museum Profiles

Type

a

0.0023435948 = product of:
  0.0046871896 = sum of:
    0.0046871896 = product of:
      0.009374379 = sum of:
        0.009374379 = weight(_text_:a in 3107) [ClassicSimilarity], result of:
          0.009374379 = score(doc=3107,freq=6.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.17652355 = fieldWeight in 3107, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=3107)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

OPACs in an increasing number of libraries are now available using the Joint Academic Network (JANET). Access has tended to be obstructed, for the casual user, by the lengthy JANET addressing codes and varying log-on procedures required by each library system. Discribed how a communications and menu package on an IBK/PC can be used so that by merely pressing cursor control, return and escape keays, any user can gain access to any one of over 40 OPACs linked to JANET

Type

a

0.0023435948 = product of:
  0.0046871896 = sum of:
    0.0046871896 = product of:
      0.009374379 = sum of:
        0.009374379 = weight(_text_:a in 3748) [ClassicSimilarity], result of:
          0.009374379 = score(doc=3748,freq=6.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.17652355 = fieldWeight in 3748, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=3748)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Discusses the factors influencing remote access to CD-ROMs: how many CD-ROM workstations are located at the place of work (single or multiple workstations); whether a PC or a CD-ROM LAN is in operation; what level of security is needed in the organisation; how many remote users need to be accomodated; and the level of software sophistication present in the staff of the organisation

Type

a

0.0023435948 = product of:
  0.0046871896 = sum of:
    0.0046871896 = product of:
      0.009374379 = sum of:
        0.009374379 = weight(_text_:a in 4758) [ClassicSimilarity], result of:
          0.009374379 = score(doc=4758,freq=6.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.17652355 = fieldWeight in 4758, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=4758)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Adaptive, in-call, bandwidth reservation may be used to enhance bandwidth utilization in a policed asynchronous transfer mode (ATM) virtual path shared by traffic streams originated by many bursty sources. Presents a model, based on Markov-modulated sources and stochastic fluid methods, for performance analysis of the proposed mechanism. The model, corroborated by simulations, is used to study achievable bandwidth gain and the effects of feedback delay and competing reservation processes

Type

a

0.002269176 = product of:
  0.004538352 = sum of:
    0.004538352 = product of:
      0.009076704 = sum of:
        0.009076704 = weight(_text_:a in 3669) [ClassicSimilarity], result of:
          0.009076704 = score(doc=3669,freq=10.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.1709182 = fieldWeight in 3669, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=3669)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This study aimed to determine if the searching behaviour of remote users of LIAS, Penn State's online catalogue differed from those using the OPAC within the library. More than 1.000 searches done by remote users (those accessing the system via either dial-access or the university's computer network) were compared to more than 1.000 searches done by in-house users. Each search was duplicated step by step and analysed according to a pre-determined set of criteria. Although few dramatic differences were found between the 2 groups, there were enough subtle differences to generate interest. In general, remote users are the more sophisticated searchers, bearing out the assumption that remote users seem to have a better conceptual knowledge of how an information system should operate. On the other hand, they struggle more with the procedural details of how to use the OPAC. Dial-access users seem to constitute a unique group of users: their searches are often quite different than those done by either network or in-house users

Type

a

0.002269176 = product of:
  0.004538352 = sum of:
    0.004538352 = product of:
      0.009076704 = sum of:
        0.009076704 = weight(_text_:a in 7706) [ClassicSimilarity], result of:
          0.009076704 = score(doc=7706,freq=10.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.1709182 = fieldWeight in 7706, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=7706)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

In Sept. 1990, the US Dept. of Education's Library Technology and Cooperation Grants Program awarded a three-year grant to the Florida Center for Library Automation (FCLA), an agency of the Florida State University System, to develop software adhering to the ANSI Z39.50 Information Retrieval protocol standard. The Z39.50 software was to operate over the OSI communications protocols and be integrated with FCLA's NOTIS system, which is shared by all 9 state universities in Florida. In order to test the correctness of its Z39.50 software, FCLA sought out other library software developers who would be willing to develop Z39.50 systems of their own. As part of this process, FCLA helped to found the Z39.50 Implementor's Group (ZIG), which has since gone on to improve the standard and promote Z39.50 implementations throughout much of the North American library systems marketplace. Early on in the project, it became apparent that TCP/IP would be a more heavily used communication vehicle for Z39.50 messages than OSI. FCLA expanded its design to include TCP/IP and, by the end of the grant in Sept. 1993, will have a working Z39.50 system that can communicate over both OSI and TCP/IP networks

Type

a

0.002269176 = product of:
  0.004538352 = sum of:
    0.004538352 = product of:
      0.009076704 = sum of:
        0.009076704 = weight(_text_:a in 3209) [ClassicSimilarity], result of:
          0.009076704 = score(doc=3209,freq=10.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.1709182 = fieldWeight in 3209, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=3209)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The IOS rererence model of open distributed processing (RM-ODP) consists of: an overview of the reference model, the descriptive model, the prescriptive model, and the architectural semantics. They provide the concepts and rules of distributed processing to ensure openness between interacting distributed application components. Openness is a combination of characteristics: accessibility, heterogeneity, autonomy and distribution. The RM-ODP introduces the concept of viewpoint to describe a system from a particular set of concerns, and hence to deal with the complexity of distributed systems. While all the viewpoints are relevant to the description and design of distributed systems, the computational and engineering models are the ones that bear most directly on the design and implementation of distributed systems. From a distributes software engineering point of view, the computational and engineering viewpoints are again the most important; they reflect the software structure of the distributed application most closely. Concentrates on the computational and engineering viewpoints

Type

a

0.002211719 = product of:
  0.004423438 = sum of:
    0.004423438 = product of:
      0.008846876 = sum of:
        0.008846876 = weight(_text_:a in 1262) [ClassicSimilarity], result of:
          0.008846876 = score(doc=1262,freq=38.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.16659044 = fieldWeight in 1262, product of:
              6.164414 = tf(freq=38.0), with freq of:
                38.0 = termFreq=38.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1262)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The Z39.50 standard for information retrieval is important from a number of perspectives. While still not widely known within the computer networking community, it is a mature standard that represents the culmination of two decades of thinking and debate about how information retrieval functions can be modeled, standardized, and implemented in a distributed systems environment. And - importantly -- it has been tested through substantial deployment experience. Z39.50 is one of the few examples we have to date of a protocol that actually goes beyond codifying mechanism and moves into the area of standardizing shared semantic knowledge. The extent to which this should be a goal of the protocol has been an ongoing source of controversy and tension within the developer community, and differing views on this issue can be seen both in the standard itself and the way that it is used in practice. Given the growing emphasis on issues such as "semantic interoperability" as part of the research agenda for digital libraries (see Clifford A. Lynch and Hector Garcia-Molina. Interoperability, Scaling, and the Digital Libraries Research Agenda, Report on the May 18-19, 1995 IITA Libraries Workshop, <http://www- diglib.stanford.edu/diglib/pub/reports/iita-dlw/main.html>), the insights gained by the Z39.50 community into the complex interactions among various definitions of semantics and interoperability are particularly relevant. The development process for the Z39.50 standard is also of interest in its own right. Its history, dating back to the 1970s, spans a period that saw the eclipse of formal standards-making agencies by groups such as the Internet Engineering Task Force (IETF) and informal standards development consortia. Moreover, in order to achieve meaningful implementation, Z39.50 had to move beyond its origins in the OSI debacle of the 1980s. Z39.50 has also been, to some extent, a victim of its own success -- or at least promise. Recent versions of the standard are highly extensible, and the consensus process of standards development has made it hospitable to an ever-growing set of new communities and requirements. As this process of extension has proceeded, it has become ever less clear what the appropriate scope and boundaries of the protocol should be, and what expectations one should have of practical interoperability among implementations of the standard. Z39.50 thus offers an excellent case study of the problems involved in managing the evolution of a standard over time. It may well offer useful lessons for the future of other standards such as HTTP and HTML, which seem to be facing some of the same issues.
This paper, which will appear in two parts, starting with this issue of D-Lib, looks at several strategic issues surrounding Z39.50. After a relatively brief overview of the function and history of the protocol, I will examine some of the competing visions of the protocol's role, with emphasis on issues of interoperability and the incorporation of semantics. The second installment of the paper will look at questions related to the management of the standard and the standards development process, with emphasis on the scope of the protocol and how that relates back again to interoperability questions. The paper concludes with a discussion of the adoption and deployment of the standard, its relationship to other standards, and some speculations on future directions for the protocol. This paper is not intended to be a tutorial on the details of how current or past versions of Z39.50 work. These technical details are covered not only in the standard itself (which can admittedly be rather difficult reading) but also in an array of tutorial and review papers (see <http://lcweb.loc.gov/z3950/agency> for bibliographies and pointers to on-line information on Z39.50). Instead, the paper's focus is on how and why Z39.50 developed the way it did, and the conceptual debates that have influenced its evolution and use. While a detailed technical knowledge of the operation of Z39.50 is certainly helpful, it should not be necessary in order to follow most of the material here. Some disclaimers are in order. I have been actively involved in the development of Z39.50 since the early 1980s and have been a participant -- and on occasion, even an instigator -- of some of the activities described here. This paper is an attempt to make a critical assessment of the current state of Z39.50 and a review of its development with the full benefit of hindsight. It recounts a number of debates that occurred within the developer community over the past years. In many of these, I advocated specific positions or approaches, sometimes successfully and sometimes unsuccessfully. What is presented here is one person's perspective - mine --, which is sometimes at odds with the current consensus with the developer community; I've tried to represent opposing views fairly, and to differentiate my opinions from fact or consensus. However, others will undoubtedly disagree with many of the comments here.

Type

a

0.0020506454 = product of:
  0.004101291 = sum of:
    0.004101291 = product of:
      0.008202582 = sum of:
        0.008202582 = weight(_text_:a in 3386) [ClassicSimilarity], result of:
          0.008202582 = score(doc=3386,freq=6.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.1544581 = fieldWeight in 3386, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3386)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Describes the development of SuperJANET, the new optical fibre network for the UK academic and research community. Considers pilot applications for SuperJANET covering library and non library applications and strategic issues to be met for SuperJANET to become an information superhighway. Gigabyte networks will be 1.000 time faster than JANET and will enable sophisticated image and voice communication. SuperJANET uses synchronous digital hierarchy technology. SuperJANET is being developed and and introduced in a number of phases. Discusses supercomputing, library and information services, and strategic issues. Examines the role of technology and librarians in the development of the virtual library

Type

a

0.0020296127 = product of:
  0.0040592253 = sum of:
    0.0040592253 = product of:
      0.008118451 = sum of:
        0.008118451 = weight(_text_:a in 3099) [ClassicSimilarity], result of:
          0.008118451 = score(doc=3099,freq=2.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.15287387 = fieldWeight in 3099, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.09375 = fieldNorm(doc=3099)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0020296127 = product of:
  0.0040592253 = sum of:
    0.0040592253 = product of:
      0.008118451 = sum of:
        0.008118451 = weight(_text_:a in 3162) [ClassicSimilarity], result of:
          0.008118451 = score(doc=3162,freq=2.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.15287387 = fieldWeight in 3162, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.09375 = fieldNorm(doc=3162)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

A special issue devoted to articles dealing with the ISO Reference Model for Open Distributed Processing

0.0020296127 = product of:
  0.0040592253 = sum of:
    0.0040592253 = product of:
      0.008118451 = sum of:
        0.008118451 = weight(_text_:a in 3208) [ClassicSimilarity], result of:
          0.008118451 = score(doc=3208,freq=2.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.15287387 = fieldWeight in 3208, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.09375 = fieldNorm(doc=3208)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0020296127 = product of:
  0.0040592253 = sum of:
    0.0040592253 = product of:
      0.008118451 = sum of:
        0.008118451 = weight(_text_:a in 1047) [ClassicSimilarity], result of:
          0.008118451 = score(doc=1047,freq=2.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.15287387 = fieldWeight in 1047, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.09375 = fieldNorm(doc=1047)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.001913537 = product of:
  0.003827074 = sum of:
    0.003827074 = product of:
      0.007654148 = sum of:
        0.007654148 = weight(_text_:a in 3102) [ClassicSimilarity], result of:
          0.007654148 = score(doc=3102,freq=4.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.14413087 = fieldWeight in 3102, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=3102)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This report presents the results of a survey of users who access the University of California's online union catalog, the MELVYL library system, via microcomputers with modems or connections carried through local or wide area networks. The report includes descriptive statistics on user location, status, subject interest, affiliation, in-library versus out-of-library usage patterns, need for assistance, and desire for new features

Type

a

0.001913537 = product of:
  0.003827074 = sum of:
    0.003827074 = product of:
      0.007654148 = sum of:
        0.007654148 = weight(_text_:a in 3108) [ClassicSimilarity], result of:
          0.007654148 = score(doc=3108,freq=4.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.14413087 = fieldWeight in 3108, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=3108)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.001913537 = product of:
  0.003827074 = sum of:
    0.003827074 = product of:
      0.007654148 = sum of:
        0.007654148 = weight(_text_:a in 4831) [ClassicSimilarity], result of:
          0.007654148 = score(doc=4831,freq=4.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.14413087 = fieldWeight in 4831, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=4831)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

CD-ROM databases are finding a permanent niche in libraries and librarians are trained both to use each new product and to keep abreast of changes in them. From the library user point of view it is possible to dial into or remotely access CD-ROM databases. Discusses the use of the communications software pcAnywhere, examines the benefits to users and libraries of remote access, and lists other areas which might be of interest to learning resource centres in regard to CD-ROM services

Type

a

0.001913537 = product of:
  0.003827074 = sum of:
    0.003827074 = product of:
      0.007654148 = sum of:
        0.007654148 = weight(_text_:a in 1589) [ClassicSimilarity], result of:
          0.007654148 = score(doc=1589,freq=4.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.14413087 = fieldWeight in 1589, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=1589)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Computer and communications technology is having a profound impact on libraries and the way in which they serve their users. Discusses online catalogues in libraries, the development of the Internet and OSI, and the development of search and retrieve (SR) protocols to allow standardized access to library catalogues across communications networks. Considers the deployment of SR protocols, problems with interoperability of clients and servers, interlibrary loan possibilities of SR protocols, and the feasibility of electronic document delivery

Type

a

0.001913537 = product of:
  0.003827074 = sum of:
    0.003827074 = product of:
      0.007654148 = sum of:
        0.007654148 = weight(_text_:a in 1895) [ClassicSimilarity], result of:
          0.007654148 = score(doc=1895,freq=4.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.14413087 = fieldWeight in 1895, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=1895)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Examines a number of possible OSI system implementation strategies based on the various prevailing system facilities: processes, threads, kernel and front-end processors. Analyzes the pros and cons of the strategies showing their relative merits in implementation. The analysis leads to the recommendation of an enhanced subsystem architecture that holds the best compromise of the conflicting requirements of modularity and efficiency

Type

a