throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`IPR Control No.: IPR2015-01444
`Attorney Docket No.: 00035-0004IP1
`
`Haller et al.
`In re Patent of:
`U.S. Patent No.: 7,039,033
`
`Issue Date:
`May 2, 2006
`Appl. Serial No.: 09/850,399
`Filing Date:
`May 7, 2001
`Title:
`
`SYSTEM, DEVICE AND COMPUTER READABLE
`MEDIUM FOR PROVIDING A MANAGED WIRELESS NETWORK USING
`SHORT-RANGE RADIO SIGNALS
`
`Declaration of Jessica Coral Sheldon-Hess
`1. My name is Jessica Coral Sheldon-Hess. I am over the age of 18, have personal knowledge
`
`of the facts set forth herein, and am competent to testify to the same.
`
`2. I earned a Master of Science in Electrical and Computer Engineering from Carnegie Mellon
`
`University in 2005 and a Master of Library and Information Science (MLIS) from the University
`
`of Pittsburgh in 2009. I have over six years of experience in the library/information science
`
`field. I have attached my Curriculum Vitae as Appendix A.
`
`3. I am a member of the American Library Association (ALA) and the Library Information
`
`Technology Association (LITA). I have served as a Councilor-at-Large for ALA and Member
`
`Services Director for ALA’s New Members Roundtable. In 2012, I was named an ALA
`
`Emerging Leader. I have given guest lectures to graduate students in library and information
`
`science, and I have presented at the state and national level to librarian and technologist
`
`audiences.
`
`4. I am fully familiar with a library cataloging standard known as the “Machine Readable
`
`Cataloging” standard, also known as “MARC,” which is an industry-wide standard method of
`
`organizing library catalog information. MARC was first developed in the 1960s by librarians at
`
`1
`
`Samsung v. IXI
`IPR2015-01444
`Exhibit 1020
`
`

`
`the Library of Congress. MARC is the primary communication protocol for the transfer and
`
`storage of bibliographic metadata in libraries.
`
`5. The Online Computer Library Center (OCLC) is a library service providing for the
`
`exchange of library materials between OCLC participating institutions. The OCLC was formed
`
`in the 1960s and now has more than 72,000 participating institutions. Participating institutions
`
`include public libraries, academic libraries, and research libraries. As of the 2014 fiscal year, the
`
`more than 72,000 participating institutions represent more than 2 billion holdings. According to
`
`a press release from OCLC in 1994, there were more than 19,000 participating institutions,
`
`which would have included hundreds, if not thousands, of public libraries; and OCLC arranged
`
`over 7 million interlibrary loans that year.
`
`6. When a library acquires a work, it often stamps the work with the date of acquisition and
`
`the name of the library where it will reside. This indicates the library’s ownership and the age of
`
`the item. Items are then placed in a processing queue. When a work is processed and formally
`
`added to the collection, the library creates a MARC record for the work in its computer catalog
`
`system. If another institution has already created a MARC record for the item, the library may
`
`choose to copy the record from OCLC into their local catalog. When a MARC record is created,
`
`OCLC automatically saves the creation date into the record; this reflects the date on which the
`
`item was first catalogued. Once the MARC record is created by a cataloger at an OCLC
`
`participating member institution, the work is available to any OCLC participating members, and
`
`therefore available to the public. The computer catalog system of the OCLC, and the MARC
`
`records included therein, are relied upon by the OCLC participating institutions during the
`
`regular course of their respective businesses.
`
`!2
`
`

`
`7. A MARC record contains several fields, each of which contains specific data about the
`
`work. For example, a work’s title is recorded in field 245. If a work is a periodical, then its
`
`publication frequency is recorded in field 310, and the publication dates (e.g., the first and last
`
`publication) are recorded in field 362, which is also referred to as the enumeration/chronology
`
`field. Field 008 is a fixed length data element field, which begins with the date the MARC
`
`record was entered on file, in the format YYMMDD. In MARC records, MARC field 040
`
`contains the OCLC or Library of Congress symbols of institutions transcribing, creating, and
`
`modifying the record. 1
`
`8. I have reviewed a copy of Exhibit 1016 submitted in IPR2015-01444. Exhibit 1016 is a
`
`book entitled “A Programmer’s Guide to JINITM Technology,” by Jan Newmarch, published in
`
`2000.
`
`9. I obtained a scanned copy of the book entitled “A Programmer’s Guide to JINITM
`
`Technology,” by Jan Newmarch from George Mason University’s (GMU’s) Fenwick Library,
`
`included as Appendix B. Although Appendix B and Exhibit 1016 have different ISBNs and a
`
`different publisher’s mark on their covers, the statement on the copyright page of Exhibit 1016,
`
`“Originally published by Apress in 2000,” suggests that the Exhibit 1016 was unchanged
`
`between printings, save perhaps for copy editing. I examined the tables of contents and the
`
` For more information about MARC fields 245, 310, 362, 008, and 040, please refer to http://
`ww.loc.gov/marc/bibliographic/bd245.html, http://www.loc.gov/marc/bibliographic/
`bd310.html, http://www.loc.gov/marc/bibliographic/bd362.html, http://www.loc.gov/marc/
`bibliographic/bd008.html, and http://www.loc.gov/marc/bibliographic/bd040.html, respectively.
`In field 040, the symbol in subfield “a” corresponds to the symbol for the institution inputting the
`original record. For a directory of OCLC symbols and their corresponding institutions, please
`refer to http://www.oclc.org/contacts/libraries.en.html. For a list of LOC symbols and
`institutions, please see http://www.loc.gov/marc/organizations/org-search.php.
`
`1 w
`
`!3
`
`

`
`indices of both Exhibit 1016 and Appendix B, and they are identical. The pagination of Exhibit
`
`1016 and Appendix B are identical, indicating that no substantive edits were made between
`
`printings. Among other pages, pages 1, 2, 23, and 24 of Exhibit 1016 and Appendix B are
`
`exactly the same, with no edits of any kind between printings. In view of the foregoing, I
`
`conclude that Exhibit 1016 is an authentic copy of the book entitled “A Programmer’s Guide to
`
`JINITM Technology.” There is no date stamp on Appendix B; however, the MARC record
`
`attached as Appendix C makes it clear that this book was publicly available in OCLC
`
`participating libraries as of January 31, 2001.
`
`10. Attached hereto as Appendix C is a true and correct copy of the MARC record for the
`
`George Mason University’s holding of the book entitled “A Programmer’s Guide to JINITM
`
`Technology.” As can be derived from Appendix C, OCLC record number 45821831 for this
`
`book was created on January 31, 2001 (field 008), by a cataloger at Fordham University (field
`
`040). Therefore, the book entitled “A Programmer’s Guide to JINITM Technology” was available
`
`to any OCLC participating members, and thereby available to the public, prior to February 20,
`
`2001.
`
`11. I have been retained on behalf of the petitioners in IPR2015-01444 to provide assistance in
`
`the above-captioned matter in establishing the authenticity and public availability of the
`
`documents discussed in this declaration. I am being compensated for my services in this matter
`
`at the rate of $100.00 per hour plus reasonable expenses. My statements are objective, and my
`
`compensation does not depend on the outcome of this matter.
`
`12. I hereby declare that all statements made of my own knowledge are true and that all
`
`statements made on information and belief are believed to be true. I further declare that these
`
`!4
`
`

`
`statements were made with the knowledge that willful false statements and the like so made are
`
`punishable by fine or imprisonment, or both, under 18 U.S.C. § 1001 and that such willful false
`
`statements may jeopardize the validity of the application or any patents issued thereon.
`
`Dated: ____________________
`
`
`
`
`
`
`
`
`
`
`
`
`____________________________________
`Jessica Coral Sheldon-Hess
`
`!5
`
`

`
`Coral Sheldon-Hess
`
`coral@sheldon-hess.org | coral.sheldon-hess.org | github.com/csheldonhess
`
`ducation:
`University of Pittsburgh – Master of Library and Information Science, 2009
`Carnegie Mellon University – MS, Electrical and Computer Engineering, 2005
`University of Virginia – BS, Electrical & Computer Engineering - With Highest Distinction, 2003
`Minors: Computer Science, Chinese Language & Culture
`
`! E
`
`
`
`Professional Experience:
`Lecturer, June 2016 - present
`University of Maryland, College of Information Studies
`• Updated and converted the course INST 630, Introduction to Programming for the Information
`Professional, to online format.
`• Will teach online section in Fall 2016.
`Librarian and Web Developer, January 2015 - present
`Freelance/Self
`• Developed, maintained, and updated websites.
`• Located items (books, articles, theses, proceedings), verified their authenticity and date of
`public availability, and wrote declarations attesting to those findings for use in patent and
`trademark litigation.
`
`Developer, September - December 2014

`Center for Open Science
`• Developed harvesters to fetch and normalize metadata from institutional and discipline
`repositories for the SHared Access Research Ecosystem (SHARE) notification service.
`• Contributed expertise about metadata and library culture to the development of the SHARE
`system architecture and discussions of COS positioning/marketing to SHARE stakeholders.
`• Contributed to the Open Science Framework with front-end (JavaScript, CSS, HTML5) and
`back-end (Python) improvements, including unit tests.
`
`Web Services Librarian/Assistant Professor, October 2009 - September 2014

`University of Alaska Anchorage/Alaska Pacific University Consortium Library
`• Designed, maintained, and improved library websites and web services.
`• Chaired Web Development Team; and proposed, designed, and chaired Social Media Team.
`• Wrote a plan for development of the library’s web presence and follow-up documents, including
`Best Practices for Topic Guides and Library Social Media Marketing Plan.
`• Trained and supported colleagues in the use of web-based technologies.
`• Served as liaison to/collection developer for School of Engineering.
`• Provided in person, phone, and online reference service.
`• Installed and customized open-source web applications (e.g. LibStats, Omeka - PHP/MySQL)
`and led acquisition and implementation of web applications purchased from vendors (e.g.
`LibGuides, LibAnswers), including coordinating policy development around their use.
`• Managed multiple content management systems, including MODX, WordPress, LibGuides, and
`Open Atrium (a constrained form of Drupal).
`• Served as Acting Head of Systems in department head’s absence (approximately 14 weeks).
`
`APPENDIX A
`
`6
`
`

`
`Coral Sheldon-Hess, CV
`Page ! of !
`2
`6
`
`Information Assistant, December 2008 - August 2009

`Carnegie Mellon University - Institutional Repository (Field Placement, Spring 2009)
`• Utilized SHERPA/RoMEO database and web to research publishers’ copyright policies.
`• Uploaded documents into Digital Commons institutional repository software and assigned
`Dublin Core metadata.
`Information Assistant, August 2008 - August 2009

`Carnegie Mellon University - Engineering & Science Libraries
`• Answered reference questions in person and remotely, utilizing engineering and science e-
`journals, databases, and print resources.
`• Processed book donations.
`• Created an engineering library blog and assisted colleagues in redesigning sections of the
`library website.
`Summer Library Assistant, April 2008 - August 2008
`Brentwood Public Library
`• Answered patrons’ reference and circulation questions and assisted with computers.
`• Checked materials into and out of the library, shelved materials, repaired damaged materials,
`and processed new materials.
`• Assisted with adult programming, including an “Intro to Blogging” class.
`Senior Consultant, June 2006 - February 2008
`Booz Allen Hamilton
`• Supported US DOT's Vehicle Infrastructure Integration (VII, now Intellidrive) program as a
`wireless systems engineer, software requirements analyst, and project manager.
`• Wrote sections of, managed subcontractors’ input to, and coordinated/edited 60+ team
`members’ contributions to the VII System Requirements Specifications.
`• Refined document creation workflows, increasing documents' accuracy and decreasing
`creation time significantly.
`• Analyzed/edited requirements for VII subsystems and applications, maintaining and updating
`requirements in Rational Requisite Pro.
`• Contributed to several proposal teams, writing a key technical section of a $93M proposal and
`writing as well as editing/coordinating authors' contributions to a $6M proposal.
`• Recruited and interviewed candidates for hire.
`RF Engineer, September 2005 - May 2006
`i5 Wireless, LLC
`• Led the company’s research and development initiatives, designing and testing antennas for
`use in waveguides within novel in-building wireless installations.
`• Monitored and performed maintenance on existing systems inside government buildings,
`including the Securities and Exchange Commission and three Library of Congress buildings.
`• Provided information about new wireless trends and emerging technologies to management.
`• Interfaced with vendors, both in coordinating the setup of the company’s new office and in
`procuring wireless test equipment. 

`Research Assistant, June 2003 - August 2005
`Carnegie Mellon University - Electrical & Computer Engineering Department
`• Performed research as part of the Antenna and Radio Communication (ARC) group and Center
`for Wireless and Broadband Networking.
`• Designed and implemented experiments that created large data sets; analyzed data in
`MATLAB.
`
`7
`
`!
`

`
`Coral Sheldon-Hess, CV
`Page ! of !
`3
`6
`
`• Provided engineering expertise to Penn DOT’s Tunnel Radio project, helping to design and
`build a system to retransmit AM and FM radio into two of Pittsburgh’s tunnels.
`• Maintained the ARC’s website.
`Honors and Awards:
`• Code4Lib 2014 Conference Diversity Scholarship Recipient
`• ALA 2012 Emerging Leader, sponsored by the ACRL Science & Technology Section
`• Pacific Northwest Library Association “LEADS” Leadership Institute, October 2010
`• UCLA student scholarship to attend Electronic Resources & Libraries 2009
`• High 5 Award (Booz Allen Hamilton), 2007 - In recognition of dedication to fostering a
`collaborative community across ITI Home Team 1 through participation in the Communications
`Focus Group.
`• Performance Recognition Award (Booz Allen Hamilton), 2006 – For outstanding support and
`dedication in developing the subsystem specifications and interface requirements for the
`Vehicle Infrastructure Integration Project.
`• Rodman Scholar (University of Virginia), 2000-2003; Echols Scholar, 1999-2000
`• William L. Everitt Student Award for Excellence (2003)
`• Eta Kappa Nu - Electrical Engineering Honors Society
`• Tau Beta Pi - Engineering Honors Society
`Professional Involvement:
`• American Library Association (2008-present)
`• ALA Councilor-at-Large (2013-14)
`• New Members Round Table (2008-14)
`• Member Services Director (2011-13)
`• Student and Student Chapter Outreach Committee (2008-10), Chair (2009-10)
`• Web Committee (2009-10), Chair (2013-14)
`• Library Information Technology Association (LITA) (2009-present)
`• LITA Local Task Force (2016-present)
`• Code4Lib
`• Conference Documentation Committee (2015-present)
`• Conference Accessibility Committee (2016-present)
`• In the Library with the Lead Pipe (open access journal), Tech Lead (2013-15)
`• Code for America - Anchorage (2013-14), Pittsburgh (2015-present)
`• Anchorage Programming Workshop (2013-2015)
`• Co-founder and co-host
`• Teacher/trainer
`• Alaska Library Association (2009-14)
`• Anchorage Chapter – President (2011), Past-President (2012-13)
`• New Members Roundtable – Chair (2011-12)
`• AkLA Annual Conference – Technology Coordinator (2010), Website Chair (2014)
`• Social Media Committee (2010-present), Chair (2013-14)
`• Web Team (2012-14)
`• Alaska Library Snapshot Day Committee (2011, 2012)
`
`8
`
`!
`

`
`Coral Sheldon-Hess, CV
`Page ! of !
`4
`6
`
`!C
`
`onference Presentations and Panels:
`• “Command Line Bootcamp,” Co-leader, Code4Lib Preconference, 3/7/2016.
`• “Level Up Your Coding with Code Club (yes, you can talk about it),” Code4Lib, 2/10/2015.
`• “Open source could save libraries! Maybe!,” Open Source Bridge, 6/24/2014.
`• “Technology, Librarianship, and Gender: Moving the conversation forward” (full day pre-
`conference, co-moderator) – “Codes of Conduct” (mini-session moderator), Code4Lib.
`3/24/2014.
`• “Battledecks!,” (deck builder/MC), Alaska Library Association Annual Conference, 2014.
`• “Tune in, Turn on, and Get Social,” Panel Member, Alaska Library Association Annual
`Conference, 3/2/2014.
`• “Challenges of Gender Issues in Technology Librarianship,” Panel Discussion, ALA Midwinter
`Meeting, 1/25/2014.
`• “Getting buy-in on user centricity,” LITA National Forum, 11/10/2013.
`• “Anchorage Programming Workshop,” Anchorage Mini-Maker Faire, 7/27/2013.
`• “Back in the Stacks, Bringing Professional Organization into Professional Life,” ACRL New
`Members Discussion Group Panel Discussion at ALA Midwinter, 1/27/2013.
`• “Librarians Build Communities: Advocacy Through Volunteerism,” Pacific Northwest Library
`Association Annual Conference, 8/3/2012.
`• “Emerging Leaders Team Seeking States to Host Librarians Build Communities,” ALA Advocacy
`Corner, American Library Association Annual Conference, 6/24/2012.
`• “Alaskan Librarians Build Communities,” Alaska Library Association Annual Conference –
`Lightning Talks, 2/25/2012.
`• “Social Media Starter Kit,” Alaska Library Association Annual Conference, 2/18/2011.
`• “Implementing New Tech Tools,” DirLead (Alaska Public Library Directors’ Leadership Group)
`Annual Meeting, 10/15/2010.
`• “ALA Conference for Students and Introduction to NMRT,” Chapter Meeting, Virginia/West
`Virginia branch of the University of North Texas’s Library and Information Sciences Student
`Association (LISSA), 6/21/10.
`
`Workshops and Training Sessions:
`• “Getting buy-in on user-centricity.” Guest lecture for LIS 861, UW-Madison School of Library
`and Information Science. 5/5/14.
`• “Intro to the Command Line.” Anchorage Programming Workshop. 2/19/14.
`• “WordPress Basics.” Anchorage Programming Workshop. 10/16/13.
`• “Technology Training for Part-Time Librarians.” UAA/APU Consortium Library. 8/19/13.
`• “LibChat Training.” Training for Instruction & Reference Department, UAA/APU Consortium
`Library. 8/6/13.
`• “Introduction to GitHub.” Anchorage Programming Workshop. 7/31/13.
`• “LibCal Training (Using Calendars).” Training for UAA/APU Consortium Library faculty and staff.
`5/23/13, 5/28/13, and 6/11/13.
`• “Web Fundamentals.” Anchorage Programming Workshop. 5/22/13.
`• “Twenty-Minute Training: Blogging Best Practices.” UAA/APU Consortium Library’s Library,
`Reference, and Information Technology Training Series. 4/9/13.
`• “Using QuickSearch for Library Research.” UAA Faculty ETech Fair. 2/15/13
`• “LibAnswers Policies & How-to.” Training for Instruction & Reference Department, UAA/APU
`Consortium Library. 11/27/12.
`• “LibCal Training (Moderating Room Booking).” Training for Circulation staff, UAA/APU
`Consortium Library. 11/8/12 and 11/9/12.
`
`9
`
`

`
`Coral Sheldon-Hess, CV
`Page ! of !
`5
`6
`
`• “Twenty-Minute Training: LibAnswers QuerySpy: Answering Questions Our Users Wanted to
`Ask.” UAA/APU Consortium Library’s Library, Reference, and Information Technology Training
`Series. 11/6/12.
`• “Twenty-Minute Training: LibAnswers.” UAA/APU Consortium Library’s Library, Reference, and
`Information Technology Training Series. 8/28/12.
`• “Using LibAnswers.” Training for Instruction & Reference Department, UAA/APU Consortium
`Library. 8/14/2012.
`• “Adding FAQs to the LibAnswers Knowledge Base.” Training for Instruction & Reference
`Department, UAA/APU Consortium Library. 8/7/2012.
`• “Writing to the Reference Blog.” Training for Instruction & Reference Department, UAA/APU
`Consortium Library. 7/31/2012.
`• “Using LibCal Room Booking.” Training for Circulation staff, UAA/APU Consortium Library.
`7/9/2012 and 7/13/2012.
`• “Google+.” Faculty ETech Fair, presented by UAA ELearning Working Group. 2/17/12.
`• “Twenty-Minute Training: Google Plus.” UAA/APU Consortium Library’s Library, Reference, and
`Information Technology Training Series. 2/14/2012.
`• “LibGuides Open Work Session.” Training for UAA/APU Consortium Library faculty and staff.
`12/14/11, 1/11/12, 7/16/13, 7/30/13, 8/12/13, 8/15/13, 8/21/13, 8/23/13.
`• “Twenty-Minute Training: RSS and Google Reader.” UAA/APU Consortium Library’s Library,
`Reference, and Information Technology Training Series. 7/26/2011.
`• “Twenty-Minute Training: Facebook Privacy.” UAA/APU Consortium Library’s Library,
`Reference, and Information Technology Training Series. 10/26/2010.
`• “Twitter in the Classroom,” UAA CAFE Cloud Computing in the Classroom Workshop.
`3/26/2010.
`
`Faculty Service:
`UAA/APU Consortium Library
`• Engineering Librarian Search Committee (Spring & Summer 2013)
`• Banned Books Week Planning Committee Member (2012)
`• Display contributor: National Poetry Month (2012 & 2013)
`• Staff Development Committee (2010-12)
`• English Librarian Search Committee (Summer 2011)
`• Exhibit contributor, two pieces: Library Art Show, ARC Gallery (March 2011)
`• Electronic Resources Librarian Search Committee (Spring & Summer 2011)
`• Exhibit contributor: Eye of the Beholder 3: One Image, Many Perspectives (October 2010)
`University of Alaska Anchorage
`• Commencement – Hooding Ceremony (2010 and 2011)
`• Faculty Senator (2013-14)
`• Academic Computing, Distance Learning, Information Technology and eLearning (ACDLITe)
`Committee
`• eLearning Working Group (2009-14), subcommittees:
`• UA Google Apps
`• Social Media in Education
`• Mobile Use Survey (Chair, 2013)
`• Cloud Computing
`• SafeAssign
`• Blackboard Shell
`• Sharepoint
`
`10
`
`!
`

`
`Coral Sheldon-Hess, CV
`Page ! of !
`6
`6
`
`Community
`• Alaska Hackathon participant, organizing committee member (2013-14)
`• American Diabetes Association Tour de Cure - Team Captain (2011-2013)
`• Anchorage Citywide Cleanup - organizer, AkLA-Anchorage (2011, 2012, 2013)
`Professional Development:
`• Abstractions (upcoming, 2016)
`• Pittsburgh TechFest (2016)
`• Code4Lib Conference (2014, 2015, 2016)
`• The Data Scientist’s Toolbox, Johns Hopkins University (2015)
`• Open Source Bridge (2014)
`• AdaCamp (2014)
`• Library Information Technology Association Forum (2013)
`• Developing a Web Analytics Strategy for Your Library: Using Data to Measure Success - ALA
`LITA Preconference (1/25/13)
`• Getting to Wow: Customer Service Training (1/9/13)
`• Consortium Library Reference Training Series (2009-14)
`• UAA Faculty Technology Center TechCamp: InDesign (8/10/12)
`• Pacific Northwest Library Association Annual Conference (2012)
`• Alaska Library Association Annual Conference (2009-14)
`• American Library Association Annual Conference (2008-12)
`• American Library Association Midwinter Conference (2010, 2012-14)
`• ALA Emerging Leaders program (2012)
`• The Future of Libraries (5/3/12)
`• How to Deliver Great Customer Service (4/19/12)
`• LITA Preconference: User Experience Design for Websites (6/24/11)
`• ASIST&T Introduction to Information Architecture Webinar (1/14/11)
`• CIOS A152 - Digital Imaging Concepts & Applications: Photoshop (UAA, spring 2011)
`• Trendy Topics: Social Media: Twitter, Facebook, and More, an Online Conference (arranged for
`colleagues and attended) (4/20/11)
`• PNLA Leads Leadership Institute (10/2010)
`
`11
`
`!
`

`
`APPENDIX B
`
`5
`NIVERSITY LIBRARIE - MU
`
`I!
`
`N I WW
`IN!
`ll!!! Hi!
`
`
`
`
`BE???/DLEfilH?EE
`
`III!
`
`
`
`
`
`
`
`@
`
`A Programmer’s Guide
`to Jini“ Technology
`
`Up—to—date coverage of the newest Iinim features announced by Sun this year
`
`#
`
`Addresses important topics such as application architecture, user interfaces for Iinim services,
`
`and how hardware devices and CORBA fit in with the Iinim framework
`
`IV
`
`Tech reviewed by master Java“ programmer and wel1—l<now11 columnist Bill Venner
`
`
`
`Apressw
`
`APPENDIX B
`
`12
`
`

`
`A Programmer’s Guide to
`Jini“ Technology
`
`IAN I)/I,EW1\/LARCH
`
`GWWGE MA$QN LINIVERSITV
`UNIVERSITY LIBRARIES
`
`13
`
`

`
`A Programmer's Guide to IiniTM Technology
`Copyright ©2000 by Ian Newmarch
`
`All rights reserved. No part of this work may be reproduced or transmitted in any form or by any
`means, electronic or mechanical, including photocopying, recording, or by any information
`storage or retrieval system, without the prior written permission of the copyright owner and the
`publisher.
`
`ISBN (pbk): l—893115-80-1
`Printed and bound in the United States of America 12345678910
`
`Trademarked names may appear in this book. Rather than use a trademark symbol with every
`occurrence of a trademarked name, we use the names only in an editorial fashion and to the
`benefit of the trademark owner, with no intention of infringement of the trademark.
`
`Editorial Directors: Dan Appleman, Gary Cornell, Karen Watterson
`
`Editor: Andy Carroll
`Production Editor: Kari Brooks
`
`Page Composition: Tony ]onick—Rappid Rabbit
`
`Artist: Karl Miyajima
`Indexer: Carol Burbo
`
`Cover: Karl Miyajima
`
`Distributed to the book trade in the United States by Springer—Verlag NewYork, Inc.,175 Fifth
`Avenue, NewYork, NY 10010
`
`and outside the United States by Springer—Verlag GmbH 8: Co. KG, Tiergartenstr. 17, 69112
`Heidelberg, Germany
`
`In the United States, phone 1-800—SPR1NGER; ordeIs@springeI-ny . com;
`http : //www. spIingeI- ny . com
`
`Outside the United States, contact orders@springer. de;
`http : //www. springer. de; fax +49 6221 345229
`
`For information on translations, please Contact Apress directly at 901 Grayson Street, Suite 204,
`Berkeley, CA, 94710
`
`Phone: 510-549-5931; Fax: 510-549-5939; info@apress . com; http : //www.apress . com
`The information in this book is distributed on an "as is" basis, without warranty. Although every
`precaution has been taken in the preparation of this work, neither the author not Apress shall
`have any liability to any person or entity with respect to any loss or damage caused or alleged to
`be caused directly or indirectly by the information contained in this work.
`
`14
`
`

`
`Contents at a Glance
`
`Introduction .................................................................. .;............................... ..xix
`
`Chapter 1 Overview of Jini ...................................................................... ..1
`
`Chapter 2 Troubleshooting Jini
`Configuration Problems .......................................................................... ..17
`
`Chapter 3 Discovering a Lookup Service ........................................... ..23
`
`Chapter 4 Entry Objects ........................................................................... ..43
`
`Chapter 5 Service Registration ........................................ I .................. ..49
`Chapter 6 Client Search .......................................................J....................57
`
`Chapter 7 Leasing ....................................................................................... ..63
`
`Chapter
`
`A Simple Example ......................................................................83
`
`Chapter
`
`Choices for Service Architecture ...................................109
`
`Chapter 10 Discovery Management ........................................................ ..153
`
`Chapter 11
`
`Join Manager ...................................................;..................... ..161
`
`Chapter 12 Security ................................................................................. ..169
`
`Chapter 13 More Complex Examples ................ J......................................193
`
`Chapter 14 Remote Event ......................................................................... ..235
`
`Chapter 15 ServiceDiscoveryManager....................................................255
`
`Chapter 16 Transaction ........................................................................... ..271
`
`Chapter 17
`
`LEGO MINDSTORMS .................................................................. .. 295
`
`Chapter 18
`
`CORBA and Jini ..................................................................... ..323
`
`Chapter 19 User Interfaces for Jini Services ................."a........ ..355
`
`Chapter 20 Activation ............................................................................. ..393
`
`Index .................................................................................................................. "433
`
`15
`
`

`
`Contents
`
`Introduction ................................................................................................... "xm
`
`Chapter 1 Overview of Jini ............................................................... "1
`
`Jini ............................................................................................................................. "1
`
`Components ................................................................................................................ "2
`
`Service Registration .......................................................................................... "3
`
`Client Lookup ......................................................................................................... "5
`
`Proxies ...................................................................................................................... "7
`
`Client Structure .............................W’................................................... H.............."8
`
`Server Structure ................................................................................................ "10
`
`Partitioning an Application ........................................................................ "11
`
`Support Services ........ .{...................................................................................... "13
`
`HTTP Server ...........................
`
`......................................................................... .. 13
`
`RMI Daemon ..................................................................................................... ..15
`
`Summary .................................................................................................................... "15
`
`Chapter 2 Troubleshooting Jini
`' Configuration Problems ............................................. "17
`
`Java Packages ....................................................................................................... "17
`
`Jini Versions ....................................................................................................... "18
`
`16
`
`

`
`Jini Packages ............................................................... i...................................... "19
`
`ummpSmvRe ..................................................................................................... .20
`
`RMI Stubs ................................................................................................................ ..20
`
`Debugging ................................................................................................................ "22
`
`Summary .................................................................................................................... "22
`
`Chapter 3 Discovering a Lookup Service .............................. ..23
`
`Running a Lookup Service ............................................................................... "23
`Reggie ................................................................................................................. ..23 M
`
`rmid and IDK 1.3 ......................................................................................... .I;.....26
`
`Unicast Discovery ............................................................................................... "26
`
`Loo1<upLocator ............... ..- ................................................................................. ..27
`
`Inva1idLookupLocator.............................................. ..g.: ..................................... ..27
`
`Running the Inva1idLookupLocat0r ................................................................ ..29
`
`Information from the LookupLocator ............................................................. ..29
`
`getRegistrar ........................................................................................................ ..30
`Running the UnicastRegister............................................................................ ..32
`
`Broadcast Discovery .......................................................................................... "32
`
`Groups ..........

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket