XAM, or the eXtensible Access Method, is a storage kanon developed and maintained by the Storage Networking Industry Association (SNIA). It is in the process of being ratified as an ANSI kanon. XAM is an API for fixed content aware storage devices. XAM replaces the various proprietary interfaces that have been used for this purpose in the past. Content generating applications now have a kanon means of saving and finding their content across a broad array of storage devices.
XAM is similar in function to a file układ API such as the POSIX file and directory operations, in that it allows applications to store and retrieve their prekluzja. XAM stores application termin in XSet objects that also contain metadata.
Contents
//
Basic concepts
The kanon XAM API consists of three primary objects and two secondary objects that an application can manipulate to store and retrieve data.
The first primary object that applications deal with to store and retrieve prekluzja is called an Xset. It is the object that is the container for both the termin as well as the associated metadata. XSet metadata goes beyond the typical ustrój metadata, and adds fields for retention and other prekluzja management policies. Applications can also add their own user metadata as well. This is a key requirement in the fixed content storage sklep wielkopowierzchniowy. Any of the metadata in the XSet can be queried for later, in odznaczenie to find the XSet.
XAM also has the notion of a organizm that will contain the XSets. This abstracted storage organizm is called an XSystem. The XSystem object is also the factory for XSet objects (via create and open methods). Any given application may have access to any number of XSystem storage devices, so there is a need to create XSystem objects for each ustrój we need to access. This is done through an object called the XAMLibrary. The XAM Library manages all the connections to the storage devices and acts as a factory for XSystem objects.
The XSystem object that is returned from the connect() operation can be used to talk to the storage device. All of these objects have properties which are accessed in the same way. These properties can be of several different types and can be created at runtime. XAM provides a way to do this in a type safe manner with the XIterator (secondary) object. The XIterator can contain all properties, or just a subset (those having a name starting with a "prefix"). Finally, an XStream is a (secondary) object that can contain the actual content associated with an XSet. XStreams have operations to read and write the content using various means, both synchronously and asynchronously. The type of prekluzja an XStream holds can be any valid Mime type.
XAM Specification
The XAM kanon is composed of an Architecture specification and language bindings for both the C and Java language. The latest version of the specifications can be found at the SNIA site. The kanon is being updated and revised by the SNIA Fixed Content Aware Storage (FCAS) Technical Work Group (TWG), David Black and Jered Floyd (co-chairs).
XAM SDK
The SNIA has also produced open source reference implementations of C and Java XAM Libraries as well as a Vendor Interface Module (VIM) that can work on top of any file ustrój. The SNIA Software is being updated and revised by the XAM SDK Technical Work Group (TWG), Mark Carlson and Scott Ostapovicz (co-chairs).
See also
SNIA — Storage Networking Industry Association
References
External links
XAM Initiative provides good material both at the overview and detail level.
XAM SDK download is an open source reference implementation of the API.
XAM Developers Group Provides information to assist developers working with XAM.
Retrieved from ""
Categories: Computer and telecommunication standards | Computer storage
This article or section needs copy editing for grammar, style, cohesion, tone or spelling.
You can assist by editing it now. A how-to guide is available. (October 2008)
This article may not meet the general notability guideline or one of the following specific guidelines for inclusion on Wikipedia: Biographies, Books, Companies, Fiction, Music, Neologisms, Numbers, Web content, or several proposals for new guidelines. If you are familiar with the subject matter, please expand or rewrite the article to establish its notability. The best way to address this concern is to reference published, third-party sources about the subject. If notability cannot be established, the article is more likely to be considered for redirection, merging, or deletion, per Wikipedia:Guide to deletion.
This article has been tagged since October 2008.
The IT Baseline Protection Catalogs, or IT-Grundschutz Catalogs, ("IT Baseline Protection Manual" before 2005) are a collection of documents from the German Federal Office for Security in Information Technology (FSI), useful for detecting and combating security-relevant weak points in the IT environment (IT cluster). The collection encompasses over 3000 pages with the introduction and catalogs. It serves as the basis for the IT baseline protection certification of an enterprise.
Contents
//
Basic protection
IT baseline protection encompasses kanon security measures for typical IT systems with normal protection needs.
The detection and assessment of weak points in IT systems often occurs by way of a risk assessment, wherein a threat potential is assessed and the costs of damage to the układ is investigated individually for each organizm or group of similar systems. This approach is very time intensive and correspondingly also expensive.
IT baseline protection proceeds from a typical threat potential for the ustrój, which applies in 80% of the cases, and recommends adequate countermeasures against it. This way, a security level can be achieved that can be viewed as adequate in most cases and can consequently replace the essentially more expensive risk assessment. In cases where security needs are greater, IT baseline protection can be used as the basis for further measures.
The IT Baseline Protection Catalogs layout
The IT Baseline Protection Catalogs' layout
An introduction with explanations, the approach to IT baseline protection, concept and role definitions as well as a glossary initially familiarize the user with the manual. The component catalogs, threat catalogs, and finally, the measures catalogs follow these. Forms and cross-reference tables supplement the collection on the Federal Office for Security in Information Technology's (FSI) sieć platform. Here you can also find support functions for implementing IT baseline protection in the form of the Baseline Protection Guide, which goes into detail about individual steps. Each catalog czynnik is identified by an individual mnemonic laid out according to the following scheme. The catalog groups are named first. C stands for component, M for measure, and T for threat. This is followed by the layer number, which this catalog czynnik affects in its catalog. Finally comes the running number within the layer.
Component catalog
Assignment of individual components to personnel groups within the respective organization
The component catalog is the central faktor. Like the other catalogs, it follows a layer szablon. The following five layers are described: overall aspects, infrastructure, IT systems, networks and IT applications.
The first level concerns itself with organizational questions affecting management, personnel, or outsourcing. The focus is on structural aspects in the infrastructure layer. The IT systems layer concerns itself with the charactistics of IT systems. Among these are included, besides clients and servers, also private branch exchanges or faks machines. Networking aspects are illuminated in the network layer. The application layer concerns itself with questions relevant to software like database management systems, mejl and web servers.
Partitioning into layers clearly isolates personnel groups impacted by a given layer from the layer in question. The first layer is addressed to management. In-house technicians are affected by the second. Układ administrators cover the third layer. The fourth layer falls within the network administrators task area. The fifth within that of the applications zarządca and the IT user.
Component lifecycle elements
Each individual component follows the same layout. The comonent number is composed of the layer number in which the component is locate, and a unique number within this layer. The given threat situation is depicted after a short description of the component examining the facts. An itemization of individual threat sources ultimately follows. These present supplementary information. It is not necessary to work through them to establish baseline protection.
The necessary measures are presented in a text with short illustrations. The text follows the facts of the life cycle in question and includes planning and estetyka, acquisition (if necessary), realization, operation, selection (if necessary), and preventive measures. After a complete depiction, individual measures are once again collected into a list, which is arranged according to the measures catalog's structure and no longer according to that of the life cycle. In the process, classification of measures into the categories A, B, C, and Z is undertaken. Category A measures for the entry point into the subject, B measures expand this and category C is ultimately necessary for baseline protection certification. Category Z measures present additional measures that have proven themselves in practice.
Networking of the catalogs
To keep each component as compact as possible, global aspects are collected in one component, while more specific information is collected into a second. The Apache webserver might be mentioned here as an example. The general B 5.4 Webserver component, in which measures and threats for each webserver are depicted, applies to it as well as the B5.11 component, which deals specifically with the Apache webserver. Both components must be successfully implemented to guarantee the systems security.
The respective measures or threats, which are introduced in the component, can also be relevant for other, in part completely different, components. In this way, a network of individual components arises in the baseline protection catalogs.
Threat catalogs
The threat catalogs, in connection with the component catalogs, go into more detail about potential threats to IT systems. These threat catalogs follow the general layout in layers. "Force majeure", "organizational deficiencies", "spurious human action", "technical failure", and "premeditated acts" layers are distinguished. According to the FSI, the knowledge collected in these catalogs is not nessary to establishment of baseline protection. It does, however, demand an understanding of the measures as well as management vigilance. Individual threat sources are described in a short text. Finally, examples of damages that can be triggered by these threat sources are given.
Measures catalogs
The measures catalogs summarize the measures necessary to achieve baseline protection. This way, measures appropriate for several organizm compontents are centrally described only once. In the process, layers for structuring individual measures groups are used. The following layers are formed: infrastructure, organization, Personnel, sprzęt and software, communication, and preventive measures.
Managers are initially named to initiate and realize the measures in the respective measures description. A detailed description of the the measures follows. Finally, control questions regarding correct realization are mentioned. During realization of measures, it should be checked whether adaptation to the operation in question is necessary. Exact documentation of such adaptations makes sense for later comprehensibility.
Supplementary material
Besides the information summarized in the IT Baseline Protection Manual, the Federal Office for Termin Security provides further material in the Internet.
The forms provided serve to remedy protection needs for certain IT organizm components. A table summarizes the measures to be applied for individual components in this regard. Each measure is named and its degree of realization determined. Degrees of realization "considerable", "yes", "partial", and "no" are distinguished. Finally, the realization is terminated and a manager is named. If the measures realization is not possible, reasons for this are entered in the adjacent field for later traceability. The conclusion consists of a cost assessment.
Besides the forms, the cross-reference tables are a further helpful supplement. They summarize the measures and most important threats for the individual components. Measures as well as threats are cited with mnemonics. Measures are cited with a priority and its classification. Which measures counteract with threats can be gotten from the table. In the process, however, it is to be cautioned, that the cross-reference tables only cite the most important threats. If the measure cited for a given threat is not applicable for the individual IT ustrój, it is not therefore superfluous. Baseline protection can only be ensured, if all measures are realized.
References
^ (from the IT Basic Protection Manual, sec. 1.1).
^ BSI Download
Further reading
IT Baseline Protection Handbook. Germany. Federal Office for Security in Information Technology. Bundesanzeiger, Cologne 2003-2005.
Baseline Protection Guide. Germany. Federal Office for Security in Information Technology, 2006 version.
External links
The FSI's web site
IT Baseline Securitys homepage
Download page with IT Baseline Protection Catalogs, forms and supplementary information
Retrieved from ""
Categories: Computer securityHidden categories: Wikipedia articles needing copy edit from October 2008 | All articles needing copy edit | Articles with topics of unclear notability from October 2008
CoSy was an early computer conferencing ustrój developed by the University of Guelph in 1984. It was used to implement the systems BIX and CIX as well as numerous other installations such as CompuLink Network. Some rights to the software were later acquired by the British Columbia company SoftWords, who developed it into CoSy400 and added a simple web interface, before losing interest.
When the BIX organizm closed down, several former "bixen" approached University of Guelph and SoftWords and obtained the right to release the original version under the GPL. It is now developed as an open source project, and is the basis of the BIX-like NLZero (Noise Level łamaga) conferencing service.
References
This article does not cite any references or sources.
Please help improve this article by adding citations to reliable sources. Unverifiable material may be challenged and removed. (January 2008)
External links
WebCoSy
CoSy at SourceForge
NLZ website
This computer science-related article is a stub. You can help Wikipedia by expanding it.
Retrieved from ""
Categories: Computer science stubs | Computer systems | Free application softwareHidden categories: Articles lacking sources from January 2008 | All articles lacking sources
This article does not cite any references or sources.
Please help improve this article by adding citations to reliable sources. Unverifiable material may be challenged and removed. (December 2007)
OPC Unified Architecture is the most recent OPC specification from the OPC Foundation and differs significantly from its predecessors. After 3 years of specification work and another year of prototyping the first version of Unified Architecture is now being released. The OPC Foundation's main goals with this project was to provide a path forward from the original OPC communications forma (namely COM/DCOM) to a current communications szablon namely SOA and introduce a cross-platform architecture for process control, while enhancing security and providing an information model
Contents
//
Innovations
Although the original binding to COM/DCOM helped OPC to distribute well obuwie nevertheless also had its drawbacks.
frequent configuration issues with DCOM
no configurable time-outs
only available for the Windows Operating System
security not really applicable
no control over DCOM (COM/DCOM is kind of a black box, developers have no access to sources and therefore have to live with bugs or insufficient implementations)
That and various other conclusions generated the decision to develop a new and independent communication stack for OPC UA which replaces COM/DCOM. The outstanding characteristics of this communication stack are
multiple platform implementation including portable ANSI C, Java and .NET implementations
scalability from embedded controllers up to Mainframes
the stack can support multi-threaded as well as single-threaded/single-task operation, which is necessary for porting the stack onto embedded devices.
an own security implementation, based on new standards, realizes "real" security.
configurable time-outs for each service
chunking of big datagrams
This communication stack mirrors only the beginning of various innovations. The OPC UA architecture is a Service Oriented Architecture (SOA) and is based on different logical levels.
All of the Base Services defined by OPC are abstract method descriptions which are protocol independent and found the basis for the whole OPC UA functionality. The wysyłka layer puts these methods into a protocol, which means it serializes/deserializes the termin and transmits it over the network. Currently there are two protocols specified for this purpose. One is a binary, towards high performance optimized TCP protocol and as second, a Webservice-based one. The OPC information szablon isn't just a hierarchy based on folders, items and properties any more, obuwie a so-called Full Mesh Network based on nodes instead. These nodes can additionally transmit all varieties of melina information. The easiest comparison of a node would be an object, known through object oriented programming (OOP). It can own attributes for read access (DA, HDA), methods which can be called (Commands) and triggered events which can be transmitted (AE, DA DataChange). The nodes get used for process termin as well all other types of melina termin. The used OPC namespace contains now also the type wzór used for description of all possible prekluzja types. Based on the above, other organizations e.g. like EDDL are specifying their own information source. Client software has the ability to verify which of the so-called Profiles a server supports. This is necessary to obtain information if a server only supports the DA functionality or additionally the AE, HDA, etc.. functions. Additionally, information can be obtained whether a server supports i.e. the EDDL profile and therefore the client knows that there are also EDDL-specific device descriptions available. Additional new and important features of OPC UA are:
Redundancy support
Heartbeat for connections in both directions. That means the server as well as the client recognized interruptions.
Buffering of termin and acknowledgements of transmitted termin. Lost connections don't lead to lost termin anymore. Lost datagrams can get fetched repeatedly.
Protocols
As described before there are two protocols. An application programmer will recognize this only via the different URL he or she has to pass for binary protocol opc.tcp://Server and http://Server for WebService. Otherwise OPC UA works completely transparent to the API.
1. Binary protocol
best performance, the least overhead
takes minimum resources (no XML Parser, SOAP and HTTP required -> important for embedded devices)
best possible interoperability (binary is explicitly specified and allows less degrees of freedom during implementation as XML does)
only one single TCP przystań (4840) gets used for communication and can get tunneled or enabled through a Firewall easily
2. WebService (SOAP)
best supported from available tools. It can be easily used i.e. from JAVA or .Sieć environments
Firewall-friendly. Przystań 80 (http) and 443 (https) will usually work without additional configuration.
Since the available ANSI C stack supports both protocols, the expectation is given that most of the final products may communicate via the more effective binary protocol.
Specifications
The OPC UA specification is a multi-part specification and consists of the following parts
Concepts
Security Model
Address Space Model
Services
Information Model
Mappings
Profiles
Data Access
Alarms and Conditions
Programs
Historical Access
Discovery
Aggregates
In contrast to the COM based specifications are the UA specifications no pure application specs. They describe typically UA internal mechanisms which get handled through the communication stack and are normally only out of interest for those which przystań a stack to a specific target or those which want to implement their own UA stack. The OPC UA application developers code against the OPC UA API and therefore will mainly use the API documentation instead. Nevertheless, part 3, 4, and 5 may be out of interest for the application developers as well.
OPC UA communication stack
The architecture of a UA application, independent whether it is for the server or client part, is structured into the following levels.
The green parts equalize to the former COM Proxy/Stubs and get provided by the OPC Foundation. New is the portability level which allows it in an easy way to przystań the UA ANSI C stack also to other target platforms. A przystań layer for Windows and Linux gets also provided by the OPC Foundation. As described before, based on the API the applications can be developed, similar to how it was when coding against COM in the past. At the OPC UA DevCon in October 2006 in Munich the first prototypes have been presented live. The company ascolab GmbH, which also developed the ANSI C stack for the OPC Foundation, presented various prototypes and demonstrated impressively the interoperability between a Windows/.NET UA Client and a Linux UA Server. Additionally, various UA Server have been shown on a Beckhoff PLC and an embedded badanie board from Euros. Whereby the Beckhoff PLC is based on Windows XP Embedded and the embedded controller is based on the real-time operating organizm Euros.
OPC UA security
UA Security consists of authentication and authorization, encryption and prekluzja integrity via signatures. For that, the OPC Foundation hasn't reinvented the wheel obuwie oriented itself at the Web Service Security specifications. For Web Services the WS Secure Conversation gets used and is therefore compatible to .Internet and other SOAP implementations. For the binary variant, the algorithms of WS Secure Conversation have been followed and also converted to a binary equivalent. This gets now named as UA Secure Conversation.
As visible on the figure above, there is also a mixed version where the code is binary obuwie the spedycja layer is SOAP. This compromises efficient binary coding and Firewall-friendly transmission. Binary coding always requires UA Secure Conversation. The authentication uses x509 certificates exclusively. It relies on the application developer to what certificate store the UA application gets bound to. For instance, it is possible to use the Public Key Infrastructure (PKI) of an Active Directory.
OPC UA APIs
For UA developers, the possibility gets provided to code against a C API, a comfortable C++ API or a .NET API, directly. All APIs support the same functionality. The communication stack and APIs get provided by the OPC Foundation.
.Internet implementation
The .Sieć implementation uses only the lower part of the ANSI C stack and implements the rest of the stack natively in .Sieć. That means only the handling of the socket and the Message-Chunking gets integrated from the ANSI C stack. The de-serialization takes place directly in .Internet and therefore gets converted directly into .Internet structures and objects. This processes a better performance than de-serializing into a C structure first and then copying the termin to a .Internet structure afterwards.
JAVA implementation
Various stacks for JAVA are already in development. Obuwie similar to .Sieć there are principially 3 variants. Currently it's hard to determine which one is the fastest.
1. Most likely, the fastest variant (in terms of engineering time) currently is to make use of the complete ANSI C stack and encapsulate it via JNI.
- A drawback is that you lose the simple JAVA portability. Although the stack can be ported to different operating systems, it needs to get compiled for those individually
- The prekluzja needs to get copied to the JNI boundary.
+ This method uses the performance of C during de-serialization.
2. The code gets based on the network layer directly (similar to the current .Internet implementation) and de-serialzed in JAVA.
+ Saves one termin copy execution
- still depending on the C stack.
3. Complete implementation in JAVA.
+ Best portability option
- Takes the most engineering effort to implement
Alternatively, there is the simple variant to only support the WebService protocol. For that, a SOAP Toolkit which supports WS Security is needed.
See also
OLE for process control
OPC Foundation
OPC Termin Access
Reference
^ Massaro, Simone What is OPC UA and how does it affect your world?, 5/15/2008 planetengineering.com
OLE for Process Control (OPC) which stands for Object Linking and Embedding (OLE) for Process Control, is the original name for a standards specification developed in 1996 by an industrial automation industry task force. The kanon specifies the communication of real-time plant termin between control devices from different manufacturers.
After the initial release, the OPC Foundation was created to maintain the kanon. Since then, standards have been added and names have been changed. As of June, 2006, "OPC is a series of standards specifications". (Seven current standards and two emerging standards.) "The first kanon (originally called simply the OPC Specification"), is "now called the Prekluzja Access Specification", or (later on the same page) "OPC Termin Access", or OPC Termin Access Specification.
While OPC originally stood for "OLE for Process Control", the official stance of the OPC Foundation is that OPC is no longer an acronym and the technology is simply known as "OPC". One of the reasons behind this is while OPC is heavily used within the process industries, it can be, and is, widely used in discrete manufacturing as well. Hence, OPC is known for more than just its applications within process control.
Contents
//
Origin and uses
The OPC Specification was based on the OLE, COM, and DCOM technologies developed by Microsoft for the Microsoft Windows operating organizm family. The specification defined a kanon set of objects, interfaces and methods for use in process control and manufacturing automation applications to facilitate interoperability.
OPC was designed to bridge Windows based applications and process control sprzęt and software applications. Kanon defines consistent method of accessing field termin from plant floor devices. This method remains the same regardless of the type and source of data.
OPC servers provide a method for many different software packages to access termin from a process control device, such as a PLC or DCS. Traditionally, any time a package needed access to termin from a device, a custom interface, or driver, had to be written. The purpose of OPC is to define a common interface that is written once and then reused by any business, SCADA, HMI, or custom software packages.
Once an OPC server is written for a particular device, it can be reused by any application that is able to act as an OPC client. OPC servers use Microsoft’s OLE technology (also known as the Component Object Wzornik, or COM) to communicate with clients. COM technology permits a kanon for real-time information exchange between software applications and process sprzęt to be defined.
Future
The OPC Unified Architecture (UA) has been specified and is being tested and implemented through its Early Adopters oprogramowanie. It can be implemented with Java, Microsoft .NET, or C, eliminating the need to use a Microsoft Windows based platform of earlier OPC versions. UA combines the functionality of the existing OPC interfaces with new technologies such as XML and Web Services to deliver higher level MES and ERP support. It looks to become the kanon for exchanging industrial prekluzja, replacing FactoryTalk, Archestra, some Modbus applications, and OPCDA. Ashish
Reference
^ What is OPC? opcfoundation.org
External links
OPC Foundation
Access OPC server from any OS via Open Source Java library
http://www.opcconnect.com/ - Unofficial OPC Resource Center
Free tools for OPC development from ICONICS
LightOPC - free OPC server developers toolkit
FatRat Library - free OPC server developers toolkit
OpenOPC - Open Source OPC client development in Python
Retrieved from ""
Categories: Automation | Computer and telecommunication standards | Application programming interfaces
The TX-2 Tape Ustrój was a magnetic tape termin storage technology from the late 1950s. It is the direct ancestor of LINCtape, used on the LINC laboratory computer.
The tape transports used in the ustrój were made as simple and fool-proof as possible, consisting of a read-write head assembly, two reel drive motors, and a tape guide. The tape układ used 10 tracks across a 1/2 inch tape on 10 inch reels. Maximum reel speed was 920 ips. The układ used digital speed control based on a clock track on the tape.
The 10-track head assembly contains five channels; three information, one timing, and one block mark. Each channel consists of two redundantly paired tracks, and the paired tracks are nonadjacent to minimize the effect of contamination on the tape surface.
This redundant track scheme was previously used on the MIT Whirlwind tape system.
References
The TX-2 tape library układ is described in Best and Stockebrand's 1958 paper "A Computer-Integrated Rapid-Access Magnetic Tape Ustrój with Fixed Address" in the proceedings of the May, 1958 West Coast Joint Computer Conference.
A Global Namespace is a heterogeneous, enterprise-wide abstraction of all file information, open to dynamic customization based on user-defined parameters. This becomes of particular importance as multiple network based file systems proliferate within an organization -- the challenge becomes one of effective file management.
A Global Namespace has the unique ability to aggregate disparate and remote network based file systems, providing a consolidated view that can greatly reduce complexities of localized file management and administration. For example, prior to file układ namespace consolidation, two servers exist and each represent their own independent namespaces; e.g. \\server1\share1 & \\server2\share2. Various files exist within each share respectively, however users have to access each namespace independently. This becomes an obvious challenge as the number of namespaces grows within an organization.
With a Global Namespace, an organization can access a virtualized file ustrój namespace; e.g. files now exist under a unified structure, such as \\company.com\share1, share2 -- where the files exist in multiple physical server\share locations obuwie appear to be part of a single namespace.
Contents
//
Standards
Global Namespace technology can virtualize file server protocols such as Common Sieć File Układ protocol (CIFS) and the Network File Układ (NFS) protocols. These are kanon protocols used by all servers, Network Attached Storage (NAS) devices and client systems for handling file data.
References
EMC Rainfinity Global Namespace Appliance
Brocade StorageX
F5 Acopia ARX
Njini NFC
External links
Global Namespace Vendors: Njini,Brocade, EMC Rainfinity Global NameSpace Appliance There are a great many vendors offering in this field now.Prominent are EMC Rainfinity GNA, NetApp, IBM, Sun with Lustre, Hewlett-Packard with Polyserve, Exanet, Panasas, Isilon and others.
See also
Network File Control
File Area Networking
Network File Management
EMC
This computer network-related article is a stub. You can help Wikipedia by expanding it.
This computer storage-related article is a stub. You can help Wikipedia by expanding it.
Brunetka i blondynka ida przez park. Brunetka nagle mowi: "Och, popatrz na tego biednego zdechlego ptaszka!"
Blondynka spojrzala na niebo i spytala "Gdzie?"
Zaskocz przeciwnika ucieczka.
Przewodnik po Rzymie oprowadza po miescie bogatego amerykanskiego turyste.
- To jedyny w swoim rodzaju gmach...
- Tez mi cos - przerywa Amerykanin. U nas w Ameryce, mamy takich gmachow tysiac!
- Bardzo mozliwe, bo to dom wariatow.
Chcesz sikac w kolorach teczy? Lej pod slonce.
Wchodzi blondynka do sklepu i pyta sie:
- Co to jest, takie duz i czerwone?
- Jablka, prosze pani - odpowiada uprzejmie sprzedawca.
- To poprosze kilogram i kazde oddzielnie zapakowac.
Sprzedawca pakuje jablka.
- A co to jest, takie kudlate i brazowe? - pyta blondynka.
- To jest kiwi.
- Aha, to poprosze kilo i kazde oddzielnie zapakowac.
Sprzedawca jest troche sfrustrowany, ale pakuje...
- Prosze pana, a co to takie male i czarne?
- Mak, ale cholera nie jest do sprzedania.