Search Results Heading

MBRLSearchResults

mbrl.module.common.modules.added.book.to.shelf
Title added to your shelf!
View what I already have on My Shelf.
Oops! Something went wrong.
Oops! Something went wrong.
While trying to add the title to your shelf something went wrong :( Kindly try again later!
Are you sure you want to remove the book from the shelf?
Oops! Something went wrong.
Oops! Something went wrong.
While trying to remove the title from your shelf something went wrong :( Kindly try again later!
    Done
    Filters
    Reset
  • Discipline
      Discipline
      Clear All
      Discipline
  • Is Peer Reviewed
      Is Peer Reviewed
      Clear All
      Is Peer Reviewed
  • Series Title
      Series Title
      Clear All
      Series Title
  • Reading Level
      Reading Level
      Clear All
      Reading Level
  • Year
      Year
      Clear All
      From:
      -
      To:
  • More Filters
      More Filters
      Clear All
      More Filters
      Content Type
    • Item Type
    • Is Full-Text Available
    • Subject
    • Country Of Publication
    • Publisher
    • Source
    • Language
    • Place of Publication
    • Contributors
    • Location
7 result(s) for "Cookies (Computer science) History."
Sort by:
The character of consent : the history of cookies and the future of technology policy
\"A timely history of digital consent told through the mundane yet highly contested web cookie: confronting cookies is an everyday experience for weary internet travelers, who click through and dodge cookie notifications each day. As part of an \"arrangement\" wherein services are exchanged for data, the use of cookies has been justified by notification practices like privacy policies and terms of service, and individuals \"agree\" to the arrangement by continuing on the site or clicking a box - thereby \"consenting\" to invasive data collection, analysis, and sharing\"-- Provided by publisher.
Integrating Lotus Domino 6 and WebSphere Express V5 on the IBM eServer iSeries Server
When most people enter their house, they only have to unlock one or two locks on the front door. Imagine, however, if you had to use a key and unlock the door to every room inside the house, every time you wanted to go into another room. Such is the case with many Information Technology (IT) systems these days, which require a multitude of user IDs and passwords for every system and application you want to access. Faced with growing user frustrations, many companies are turning to a single signon (SSO) security system. SSO lets users enter one user ID and password and then have access to an entire system or application.This IBM Redbooks publication is for system administrators who want to understand how to configure an SSO environment between their IBM Lotus Domino and IBM WebSphere applications on the IBM Eserver iSeries server. This environment requires using a Hypertext Transfer Protocol (HTTP) server, having a common user registry, and enabling security on both Domino and WebSphere applications.In this book, you learn how to configure and use either the Domino HTTP server or the IBM HTTP Server (powered by Apache) to serve both Domino and WebSphere content. For SSO, a Lightweight Directory Access Protocol (LDAP) server is required for common user registry between Domino and WebSphere. This book shows you how to use either Domino as the LDAP server or OS/400 Directory Services. Finally this book shows you how to enable security on both your Domino application and WebSphere Application Server - Express instance to support an SSO environment.Please note that the additional material referenced in the text is not available from IBM.
WebSphere Commerce V5.5 Handbook, Customization and Deployment Guide
This IBM Redbooks publication provides IT architects, IT specialists, and developers with the critical knowledge to design, develop, implement, deploy, and manage a WebSphere Commerce V5.5 runtime environment and store. This book includes the following:Introduction to the WebSphere Commerce runtime architecture, programming model, business and store models.Development guidelines for a e-commerce development methodology, development environment, build cycle, and globalization.ITSO B2B working example, including a business requirements analysis and solution design, and how to implement a team development environment, create and customize a store, and build, deploy, and manage a store.Deployment scenarios for implementing advanced multi-tiered runtime scenarios on Windows, Solaris, AIX and OS/400.Integration and customization with MQ, e-mail and WebSphere Commerce Analyzer.The appendixes include procedures and tips on AIX, Solaris, DB2, Oracle and WebSphere Commerce Studio implementation.Please note that the additional material referenced in the text is not available from IBM.
Windows-based Single Signon and the EIM Framework on the IBM eServer iSeries Server
Support for a Kerberos based Network Authentication Service and the introduction of Enterprise Identity Mapping (EIM) were exciting OS/400® V5R2 announcements during 2002.A Kerberos based Network Authentication Service enables the iSeries (and any kerberized application) to use a Kerberos ticket for authentication instead of a user ID and password. This enables you to sign on once in the morning to your Kerberos based security server and not be prompted again when accessing your enabled applications. This is called Single Signon (SSO).Enterprise Identity Mapping (EIM) is a cross platform solution that involves a wide range of technologies including Kerberos, LDAP, and Kerberos Network Authentication Service. Basically, EIM is a framework provided by IBM that allows the mapping of authenticated users to OS/400 (and application) userids. This extends the power of SSO to the enterprise.Because the iSeries is well known as a server that can consolidate a wide range of application programming environments into one manageable system, this IBM Redbooks publication, then, studies the implementation of Kerberos and EIM in a SCON environment that includes OS/400, Windows, and applications that are right now being updated to support the new framework. We provide easy to follow examples that demonstrate all the pieces working together.Please note that the additional material referenced in the text is not available from IBM.
IBM Web Infrastructure Orchestration
This IBM Redbooks publication provides the foundation for establishing an automatic provisioning environment of Web server solutions. The material discussed in this book provides detailed information on using the IBM BladeCenter platform as a building block for hosting a highly available, multi-tier application. The book also shows how the IBM Director and Remote Deployment Manager software products can be used to automate the deployment of WebSphere software, and demonstrates how these products can be scripted to provide hot-standby and hot-addition of blade servers to running WebSphere clusters..The additional software components of IBM Web Infrastructure Orchestration are designed to respond dynamically to Web capacity needs and utilization issues. This product bundle, based on the IBM eServer BladeCenter, consists of pre-integrated versions of WebSphere Application Server, DB2, Tivoli Storage Manager, Tivoli Monitoring, and TotalStorage hardware, coordinated by defined business policies and managed by IBM Tivoli Intelligent ThinkDynamic Orchestrator.This book is intended for an audience of experienced developers, designers, planners, network specialists, and testers of the software and hardware components listed above.
The Technological Turn
At some junction in our evolutionary history, we began to create, use, and love technology. That is what I mean by thetechnological turn. It is odd, though, for while we are a technological species, our technologies do not always appear to advance our lives. Consider this example from about a hundred years ago (Ingalls and Perez 2003; “The Tradition of the Lector,” 2004). When the Cuban cigar factories of the late nineteenth century made their way to Florida, they carried over the unique tradition of the “lector.” This individual was hired (and well paid) by the workers to read