CORBA Directory, Links. Programming, Development, Design, Support Resources, Reference @ eIT.in

Add Links: If you have a web site that you wish to include in this database, do let us know the details by sending a note about your URL to narsi@esource.in. We’ll quickly review the web site, and if found relevant, add it to the database. We look forward to web site owners and link exchange partners to submit URL. Thanks!

Looking for an outsourcing partner for application development & programming? Have you talked to us?

Other IT Web Sites from eIT.in

Content derived from Wikipedia article on CORBA

Common Object Request Broker Architecture

From Wikipedia, the free encyclopedia

The Common Object Request Broker Architecture (CORBA) is a standard defined by the Object Management Group (OMG) that enables software components written in multiple computer languages and running on multiple computers to interoperate.

Contents

1 General overview

2 Key Features

2.1 Objects by Value (OBV)

2.2 CORBA Component Model (CCM)

2.2.1 External links

2.3 Portable interceptors

2.4 General InterORB Protocol (GIOP)

2.5 Data Distribution Service (DDS)

2.6 VMCID (Vendor Minor Codeset ID)

3 Corba Location

3.1 External links

4 Problems and criticism

4.1 Fundamental flaws

4.2 Design and process deficiencies

4.3 Problems with implementations

4.4 Unsuccessful deployments

5 Notes

6 CORBA implementations

7 OMG trademarks

8 See also

9 References

10 External links

General overview

CORBA “wraps” program code into a bundle containing information about the capabilities of the code inside and how to call it. The resulting wrapped objects can then be called from other programs (or CORBA objects) across a network.

CORBA uses an interface definition language (IDL) to specify the interfaces that objects will present to the world. CORBA then specifies a “mapping” from IDL to a specific implementation language like C++ or Java. Standard mappings exist for Ada, C, C++, Lisp, Smalltalk, Java, and Python. There are also non-standard mappings for Perl, Visual Basic, and Tcl implemented by ORBs written for those languages.

This diagram illustrates how the generated code is used within the CORBA infrastructure:

This picture does not reflect all typically used possibilities. Normally the server side has the Portable Object Adapter that redirects calls either to the local servants or (to balance the load) to the other servers. Also, both server and client parts frequently have interceptors that are described below.

In addition to providing users with a language and a platform-neutral remote procedure call specification, CORBA defines commonly needed services such as transactions and security.

Key Features

Objects by Value (OBV)

Apart from remote objects, the CORBA and RMI-IIOP define the concept of the OBV. The code inside the methods of these objects is executed locally by default. If the OBV has been received from the remote side, the needed code must be either a priori known for both sides or dynamically downloaded from the sender. To make this possible, the record, defining OBV, contains the Code Base that is a space separated list of URLs from where this code should be downloaded. The OBV can also have the remote methods.

The OBV's may have fields that are transferred when the OBV is transferred. These fields can be OBV's themselves, forming lists, trees or arbitrary graphs. The OBV's have a class hierarchy, including multiple inheritance and abstract classes.

CORBA Component Model (CCM)

CORBA Component Model (CCM) is an addition to the family of CORBA definitions. It was introduced with CORBA 3, and it describes standard application framework for CORBA components. It is an extension of "language independent Enterprise Java Beans (EJB)". It provides an abstraction of entities that can provide and accept services through well-defined named interfaces called ports.

The CCM has a component container, where software components can be deployed. The container offers a set of services that the components can use. These services include (but are not limited to) notification, authentication, persistence and transaction management. These are the most-used services any distributed system requires, and, by moving the implementation of these services from the software components to the component container, the complexity of the components is dramatically reduced.

External links

Official OMG CORBA Components page

Unofficial CORBA Component Model page

Portable interceptors

Portable interceptors are the "hooks", used by CORBA and RMI-IIOP to mediate the most important functions of the CORBA system. CORBA standard defines the following types of interceptors:

IOR interceptors mediate the creation of the new references to the remote objects, presented by the current server.

Client interceptors usually mediate the remote method calls on the client (caller) side. If the object Servant (CORBA) exists on the same server where the method is invoked, they also mediate the local calls.

Server interceptors mediate the handling of the remote method calls on the server (handler) side.

The interceptors can attach the specific information to the messages being sent and IORs being created. This information can be later read by the corresponding interceptor on the remote side. Interceptors can also throw forwarding exceptions, redirecting request to another target.

General InterORB Protocol (GIOP)

The GIOP is an abstract protocol by which Object request brokers (ORBs) communicate. Standards associated with the protocol are maintained by the Object Management Group (OMG.). The GIOP architecture provides several concrete protocols:

Internet InterORB Protocol (IIOP) - The Internet Inter-Orb Protocol, is a protocol for communication between CORBA ORBs that has been published by the Object Management Group. IIOP is an implementation of the GIOP for use over an internet, and provides a mapping between GIOP messages and the TCP/IP layer.

SSL InterORB Protocol (SSLIOP) - SSLIOP is IIOP over SSL, providing encryption and authentication.

HyperText InterORB Protocol (HTIOP) - HTIOP is IIOP over HTTP, providing transparent proxy bypassing.

and many more...

Data Distribution Service (DDS)

The Object Management Group (OMG) has a related standard known as the Data Distribution Service (DDS) standard. DDS is a publish-subscribe data distribution model, in contrast to the CORBA remotely-invoked object model.

VMCID (Vendor Minor Codeset ID)

Each standard CORBA exception includes a minor code to designate the subcategory of the exception. Minor exception codes are of type unsigned long and consist of a 20-bit “Vendor Minor Codeset ID” (VMCID), which occupies the high order 20 bits, and the minor code which occupies the low order 12 bits.

Minor codes for the standard exceptions are prefaced by the VMCID assigned to OMG, defined as the unsigned long constant CORBA::OMGVMCID, which has the VMCID allocated to OMG occupying the high order 20 bits. The minor exception codes associated with the standard exceptions that are found in Table 3-13 on page 3-58 are or-ed with OMGVMCID to get the minor code value that is returned in the ex_body structure (see Section 3.17.1, “Standard Exception Definitions,” on page 3-52 and Section 3.17.2, “Standard Minor Exception Codes,” on page 3-58).

Within a vendor assigned space, the assignment of values to minor codes is left to the vendor. Vendors may request allocation of VMCIDs by sending email to tagrequest@omg.org.

The VMCID 0 and 0xfffff are reserved for experimental use. The VMCID OMGVMCID (Section 3.17.1, “Standard Exception Definitions,” on page 3-52) and 1 through 0xf are reserved for OMG use.

The Common Object Request Broker: Architecture and Specification (CORBA 2.3)

Corba Location

CorbaLoc means Corba Location and refers to a stringified object reference for a Corba object that looks similar to an URL.

All CORBA products must support two OMG-defined URLs: "corbaloc:" and "corbaname:". The purpose of these is to provide a human readable/editable way to specify a location where an IOR can be obtained.

An example of corbaloc is shown below:

corbaloc::160.45.110.41:38693/StandardNS/NameServer-POA/_root

A CORBA product may optionally support the "http:", "ftp:" and "file:" formats. The semantics of these is that they provide details of how to download a stringified IOR (or, recursively, download another URL that will eventually provide a stringified IOR).

External links

http://www.omg.org/technology/documents/formal/corba_iiop.htm

Problems and criticism

While CORBA promises to deliver much in the way code is written and software constructed, it has gathered a lot of criticism during its long history, and failed repeatedly to deliver much of its promised features, sometimes even the most fundamental ones.[1][2]

Some of its failure can be tracked down to the implementations and process in which CORBA was created as a standard, but some reflect more fundamental problems in the design, and others yet stem from the very principles on which CORBA was built.

These problems, combined on various levels, have led to a significant decline in CORBA use, and most importantly, adoption in new projects and areas, and caused the once "prodigial child" technology to degrade into an all but abandoned niche.[1]

Fundamental flaws

CORBA has a some deeply-rooted flaws on the conceptual level, which makes it impossible to fix them even in principle. One problem is the lack of a concrete goal and problems to solve. Because of this, CORBA only has a very high-level goal of "making the world a better place", but no concrete direction to go in. This has caused the standard to include technologies as different as an IPC layer, an object-oriented type system, a programming languages interoperability layer, a component system, a distributed computing platform, and more.

Another irremovable flaw in CORBA is the notion of "location transparency", ie. pretending that local (that is, residing in the same address space and accessible with a simple function call) and remote (residing anywhere else, from different processes on the same machine, to different continents) objects are really the same. This notion is fundamentally false[3], and can only be resolved in two ways: either by making all local accesses as complex as the most complex remote scenario possible, thus contradicting the very goal of simplification by unification, or by making remote objects unable to handle the failures that will occur in distributed environment, and making the resulting system provably non-robust.

Historically, CORBA contains a mixture of the above choices. Often the result was added complexity, contributing to its opinion of genuinely hard to use technology, but in some cases the design failed to acknowledge the added challenges present in distributed system, as was the case with the complete lack of security provision in the IIOP.[1]

Design and process deficiencies

In addition to the problems with the lack of well-defined goals, CORBA is often cited as a classic example of design by committee. Because there's no process in place to arbitrate between conflicting proposals, and no provisions for deciding on hierarchy of problems to attend, the standard was often created by taking a union of all features in all proposals, with no regard to coherency of the resulting creation.[1] The net result is a specification that's incredibly complex, prohibitively expensive (if at all possible) to implement, and almost impossible to understand.

To further worsen the matters, the committee that standardises CORBA is composed largely of vendors who would later implement the proposals. Because standards and easy interoperability increase competition and ease customers' movement between alternative implementations, software vendors are fundamentally disinterested in having a comprehensive standard. This leads to much of political fighting within the committee, and frequently release of standard revisions that are impossible to use without proprietary extensions.[2]

Problems with implementations

Through its history, CORBA has been plagued by shortcomings of its implementations. Oftentimes, there were no implementations available to match the published specification, and the existing ones were incomplete or inadequate. Because of the lack of requirement to provide a reference implementations, members are free to propose features which were never tested for usefulness or implementability. Implementations are further hindered by the general tendency of the standard to be verbose, and the common practice of setting compromise as a sum of all submitted proposals, which often creates APIs that are incoherent, quirky or even impossible to use, even if the individual proposals were perfectly reasonable.[1]

An example of failure to specify useful interfaces could be the BOA (Basic Object Adapter). BOA is one class of object adapters, which allow to tie the calls made by clients to abstract CORBA interfaces with actual implementations of the objects. OAs are thus necessary to actually make any objects accessible via CORBA.

However, the first version (1.0) of the spec did not specify any mechanism for such implementation, effectively making it impossible to export objects for use by clients. Version 1.1, which was the first in wider circulation, attempted to fix that by introducing a Basic Object Adapter interface.[4] As the "basic" in the name suggests, this interface was only meant as a minimal interface for simple cases. However, even as such, it had a series of elementary shortcomings, which made it impossible to use in the specified form.[5] This meant each vendor had to extend BOA to make it useful at all, and in the result made it impossible to write server code which wasn't tied to given implementation from the very beginning. This flaw in the specification was fixed only by the addition of POA (Portable Object Adapter) in CORBA 2.2, which was released full six years later, and even then was still not matched by any working implementations of the feature.

CORBA was also traditionally very hard to get a working implementation of. Implementations were complex, slow, incompatible and incomplete, yet very expensive. This was changed somewhat by availability of free implementations later, but to this day, there's virtually no freely available implementation of the 3.0 version of the standard[6], despite its release back in July 2002.

Unsuccessful deployments

Notes

^ a b c d e Rise and Fall of CORBA, a comprehensive analysis of CORBA failures, by one of its former architects, Michi Henning

^ a b Trouble with CORBA An historical essay, outlining the same problems that eventually led to CORBA's demise

^ A Note on Distributed Computing A classic paper, explaining in detail why local and remote context are fundamentally different, and the impossibility of unifying them into a single access model.

^ History of CORBA from the OMG site.

^ [1] A discussion of BOA interface and its problems.

^ [2] A listing of various, freely available CORBA implementations

CORBA implementations

An overview of available CORBA implementations

BEA Tuxedo - - A CORBA 2.5–compliant commercial ORB for Java and C++ from BEA Systems

Borland Enterprise Server, VisiBroker Ed. - - A CORBA 2.6–compliant commercial ORB for Java and C++ from Borland.

Combat - A Tcl ORB, and a Tcl layer for C++ ORBs.

e*ORB - - A commercial ORB for Ada, C and C++ from PrismTech.

ILU - An open software object interface system from Xerox PARC.

GNU Classpath - Contains the Free Software (GPL+linking exception, including newly written org.omg packages) implementation for Java.

IIOP.NET - - A Free Software (LGPL) ORB for Microsoft .NET.

JacORB - - A Free Software (LGPL) ORB implemented in Java.

J-Integra Espresso - commercial Microsoft .NET ORB by Intrinsyc J-Integra

MICO - - A Free Software (LGPL) ORB implemented in C++.

omniORB - - A Free Software (LGPL) ORB for C++ and Python.

OpenORB - - A Free Software (BSD) ORB for Java.

Orbacus - commercial C++ ORB by IONA Technologies

ORBexpress - standard and real-time commercial Ada, C++, and Java ORBs by Objective Interface Systems

ORBit2 - - A Free Software (LGPL) ORB for C, C++ and Python.

Orbix - commercial ORB by IONA Technologies

OrbRIVER - - A commercial ORB for Ada, C++ and Java from Topgraphx.

Perl ORB - - An open-source (Artistic License) ORB implemented in Perl.

PolyORB - - A Free Software (MGPL) ORB implemented in Ada.

Python ORB - - A Free Software (Python license) ORB implemented in Python.

SANKHYA Varadhi - - A commercial ORB for C++

TAO - - The ACE ORB, an open-source ORB for C++

VBOrb - - A Free Software (LGPL) ORB for Visual Basic

Xtradyne I-DBC - - A commercial CORBA Security implementation from Xtradyne.

ORBLink - A commercial ORB for Allegro Common LISP

OMG trademarks

CORBA, IIOP and OMG are the registered marks of the Object Management Group and should be used with care. Differently, the GIOP is not a registered OMG trademark. Hence in some cases may be more appropriate just to say that the application uses or implements the GIOP-based architecture. The text inside the CORBA specification itself ensures that no person shall be deemed just for using or implementing this specification.

See also

Wikibooks Programming has more about this subject:

CORBARemote procedure call (RPC)

Component technologies

Service-oriented architecture

Java remote method invocation

Web service

Distributed computing

Servant (CORBA)

Etherealization

Incarnation

Java 2 Platform, Enterprise Edition

GNOME Bonobo

KDE KPart

Internet Communications Engine

OpenAIR

References

The official CORBA standard from the OMG group (direct download, .pdf, about 10 Mb).

Robert Orfali: The Essential Client/Server Survival Guide, John Wiley & Sons, ISBN 0-471-15325-7

Robert Orfali, Dan Harkey, Jeri Edwards: The Essential Distributed Objects Survival Guide, John Wiley & Sons, ISBN 0-471-12993-3

Robert Orfali, Dan Harkey: Client/Server Programming with JAVA and CORBA, John Wiley & Sons, ISBN 0-471-24578-X

Dirk Slama, Jason Garbis, Perry Russell: Enterprise CORBA, Prentice Hall, ISBN 0-13-083963-9

Michi Henning, Steve Vinoski: Advanced CORBA Programming with C++, Addison-Wesley, ISBN 0-201-37927-9

Axel Korthaus, Martin Schader, Markus Aleksy: Implementing Distributed Systems with Java and CORBA, Springer, ISBN 3-540-24173-6

Fintan Bolton: Pure Corba, Sams Publishing, ISBN 0-672-31812-1

Jon Siegel: CORBA 3 - Fundamentals and Programming, John Wiley & Sons, ISBN 0-471-29518-3

Ron Zahavi: Enterprise Application Integration with CORBA: Component and Web-Based Solutions, John Wiley & Sons, ISBN 0-471-32720-4

Bret Hartman, Konstantin Beznosov, Steve Vinoski, Donald Flinn: Enterprise Security with EJB and CORBA, John Wiley & Sons, ISBN 0-471-40131-5

Thomas J. Mowbray, Ron Zahavi: The Essential Corba: System Integration Using Distributed Objects, John Wiley & Sons, ISBN 0-471-10611-9

Michael Rosen, David Curtis: Integrating CORBA and COM Applications, John Wiley & Sons, ISBN 0-471-19827-7

Gerald Brose, Andreas Vogel, Keith Duddy: Java Programming with CORBA, John Wiley & Sons, ISBN 0-471-37681-7

John Schettino, Robin S. Hohman, Liz O'Hara: CORBA For Dummies, Hungry Minds, ISBN 0-7645-0308-1

Jeremy L. Rosenberger: Teach Yourself CORBA in 14 Days, Sams Publishing, ISBN 0-672-31208-5

Jon Siegel: Quick CORBA 3, John Wiley & Sons, ISBN 0-471-38935-8

Thomas J. Mowbray, Raphael C. Malveau: CORBA Design Patterns, John Wiley & Sons, ISBN 0-471-15882-8

Robert Orfali, Dan Harkey, Jeri Edwards: Instant CORBA, John Wiley & Sons, ISBN 0-471-18333-4

Paul Harmon, William Morrissey: The Object Technology Casebook, John Wiley & Sons, ISBN 0-471-14717-6

External links

OMG CORBA 3

Object Management Group

Information Board

Catalog of OMG Specifications

IDL / Language Mapping

CORBA Component Model (CCM)

IIOP

Services

Facilities

Domain

Embedded Intelligence

Security

UML, MOF, XMI, CWM

Description by Christopher B. Browne

CORBA support for autoconf

discussions

OrbZone forum

CORBA Resources & Links

Article "XML as CORBA Data" by Douglas C. Schmidt and Steve Vinoski

Article "Building Distributed Applications with Corba and XML" by Dermot Russell and Nick Simha

SOAP Bridge

Article "Rise and fall of CORBA" by Michi Henning

Retrieved from http://en.wikipedia.org/wiki/Common_Object_Request_Broker_Architecture

End of Wikipedia content, http://en.wikipedia.org/wiki/CORBA

Web Resources for CORBA

More eIT.in References

Software

· Programming & Development Directory

o Software Design & Development Methodologies

§ Adaptive Project Framework

§ Agile Software Development

§ Crystal Methods

§ Dynamic Systems Development Model (DSDM)

§ Extreme Programming (XP)

§ Feature Driven Development (FDD)

§ Information Technology Infrastructure Library (ITIL)

§ Joint Application Development (JAD)

§ Lean Development (LD)

§ Unified Process

· Rational Unified Process (RUP)

§ Object Oriented Programming

· COM

· CORBA

· EJB

§ Rapid Application Development (RAD)

· PowerBuilder

§ Scrum

§ Spiral

§ Systems Development Life Cycle (SDLC)

§ Waterfall

o Programming Languages

§ The A-Z of Programming Languages

§ A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z

Main Sections @ eIT.in

Software

· Free & Open Source Software

· Operating Systems

o Mainframe & Legacy Operating Systems

· Midrange

· Mainframe Operating Systems

· Databases

· Programming & Development Directory

o Programming Languages

§ The A-Z of Programming Languages

§ A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z

· Internet & Web

§ Web Servers

§ Application Servers

§ Server Side Scripting

§ Web Services

Computer Hardware
Networking & Communications Technologies
IT Strategy & Design
IT in Industries & Businesses
IT in Functions & Business Processes

IT Infrastructure
Tech Support
IT, Software Industry, Trade & Business Network
IT, Software Industry News & Updates

About eIT.in

eIT.in is a comprehensive directory for everything IT & Software. It contains over 500 categories, and well over 10,000 web resources

eIT.in provides directory and web links resources for the IT, software, programming & software development domains. It is intended to be useful for application, applications programmers & developers, software technology programmer & developer, databases software development, administrators & DBAs, application developers, strategy architect, design specialists and architects, migration, integration, customization consultants and customisation analysts, administration, maintenance & support professionals, outsourcing consultant, bespoke solutions programming developers & coders, project management & functional analyst, and for system administrators, testing & quality control engineers. It will make an effort to provide resources on tutorial/tutorials, guide, guides, tips, faq, faqs on these topics.

eIT.in content is available under GPL: All directory content at mainframe.in is under the General Public License (GPL). Under this license, anyone is free to copy & use any amount of directory content @ eIT.in, make changes to it and use it in any way they wish, as long as they also allow the same rights to anyone else for this content. The concept of GPL has been adapted from the GNU GPL of the Free Software Movement. To those who wish to use content from eIT.in, our only request is that they acknowledge the source and provide a link back to eIT.in. This is only a request!

Countries & Cities Where eIT.in Provides Assistance

eIT Cities: Bangalore, Chennai, Mumbai, Bhubaneswar, Mysore, Kolkaka, Delhi, Pune, Trivandrum, Hyderabad

You are the $$$ Section of eIT.in

Reference

GeoDig – Get Local!

Have you checked out the GeoDig directories for over 30 countries? GeoDig provides useful local and regional web resources for over 200 cities around the world. See the list of cities and countries for which GeoDig provides locality-specific web resources.

North America

USA - Alabama (AL) > Birmingham; Alaska; Arkansas (AR) > Little Rock; Arizona (AZ) > Phoenix, Las Vegas, Tucson; California (CA) > Los Angeles, San Francisco, Sacramento, Fresno, Bakersfield; Colorado, CO > Denver; Connecticut, CT > Hartford; District of Columbia, DC > Washington DC; Delaware (DE) > Wilmington; Florida > Miami, Orlando, Tampa, Orlando, Sarasota, West Palm Beach, Jacksonville; Georgia > Atlanta; Hawaii > Honolulu; Idaho; Illinois > Chicago; Indiana > Indianapolis; Iowa; Kansas (KS); Kentucky (KY) > Louisville; Louisiana (LA) > New Orleans, Baton Rouge; Maine; Maryland (MD) > Baltimore; Massachusetts > Boston, Springfield; Michigan > Detroit, Grand Rapids; Minnesota > Minneapolis-St. Paul; Mississippi (MS); Missouri (MO) > Kansas City, St. Louis; Montana; Nebraska (NE) > Omaha; Nevada (NV) > Las Vegas; New Hampshire; New Jersey (NJ) > Jersey City, Newark; New Mexico (NM) > Albuquerque; New York > New York, Buffalo, Rochester, Albany, Syracuse; North Carolina (NC) > Raleigh-Durham, Charlotte, Greensboro; North Dakota; Ohio> Columbus, Cincinnati, Cleveland, Toledo, Youngstown, Dayton; Oklahoma (OK) > Oklahoma City, Tulsa; Oregon > Portland; Pennsylvania > Philadelphia, Allentown, Pittsburgh, Harrisburg, Scranton, ; Rhode Island (RI) > Providence; South Carolina (SC) > Greenville; South Dakota; Tennessee (TN) > Knoxville, Memphis, Nashville; Texas > Austin, Dallas, Houston, San Antonio, El Paso, Austin, McAllen; Utah (UT) > Salt Lake City; Vermont; Virginia (VA) > Norfolk, Richmond; Washington > Seattle; West Virginia; Wisconsin (WI) > Milwaukee; Wyoming

Canada - Vancouver, Montreal, Toronto, Calgary, Ottawa-Gatineau, Edmonton, Quebec City, Winnipeg, Hamilton, London

You are the $$$ Section of eIT.in

Europe - UK - London, Glasgow, Manchester, Birmingham, Liverpool, Sheffield, Leeds, Bristol, Edinburgh, Leicester; France - Paris, Marseille, Lyon, Toulouse, Nice, Nantes, Strasbourg, Montpellier, Bordeaux; Germany - Frankfurt (Frankfurt am Main), Munich (München), Berlin, Düsseldorf, Hamburg, Cologne (Köln), Essen, Dortmund, Stuttgart, Bremen, Duisburg, Hannover, Nürnberg (Nuremberg), Dresden, Leipzig; Italy - Milan (Milano), Rome (Roma), Napoli (Naples), Torino (Turin), Palermo, Bologna, Firenze (Florence), Genova (Genoa); Spain - Madrid, Barcelona, Valencia, Sevilla, Zaragoza, Malaga, Murcia, Las Palmas, Bilbao; Scandinavia - Finland - Helsinki (Helsingin), Espoo, Tampere (Tampereen), Vantaa, Turku, Oulu, Sweden - Stockholm, Goteborg (Göteborg), Malmo (Malmö), Uppsala, Vasteras (Västerås), Denmark - Copenhagen (Københavns), Aarhus (Århus), Odense, Aalborg (Ålborg), Norway - Oslo, Bergen, Stavanger, Trondheim; Benelux - Belgium - Brussels (Brussel), Antwerp (Antwerpen), Ghent (Gent, Gand), Charleroi, Liège (Liege), Netherlands - Amsterdam, Rotterdam, Utrecht, Eindhoven, Tilburg, ‘s-Gravenhage (sGravenhage), Groningen, Luxembourg - Luxembourg City; Portugal – Lisbon; Greece – Athens; Hungary – Budapest; Poland – Warsaw; Switzerland - Zürich (Zurich), Geneva (Geneve, Genève), Basel, Bern (Berne), Lausanne; Austria - Linz, Vienna (Wien), Graz, Linz, Salzburg, Innsbruck; Ireland – Dublin

Asia - India - Mumbai, New Delhi, Bangalore; China & Hong Kong - Hong Kong, Beijing, Shanghai, Tianjin, Wuhan, Shenyang, Guangzhou, Harbin, Xian; Japan - Tokyo, Osaka, Yokohama, Nagoya, Sapporo, Kyoto, Kobe, Fukuoka, Kawasaki, Hiroshima; South Korea - Seoul, Pusa, Taegu, Incheon, Taejeon, Taiwan - Taipei; Malaysia - Kuala Lumpur; Singapore; Russia - Moscow, St Petersburg

You are the $$$ Section of eIT.in

Middle East - Turkey - Istanbul, Israel - Tel Aviv

Oceania - Australia - Sydney, Melbourne, Brisbane, Perth, Adelaide

Africa - South Africa - Johannesburg, Cape Town, Durban

eIT.in is a product of eSource India & Sourcing India

Other eSource & Sourcing sites: IT & Software (Dir, SAP), BPO, Chemicals, Textiles, Plant Oils, dotMobi, Billion Dollar Questions,

Biodiesel Encyclopedia, Linens, ideOS, Follars – Free, Open-source Dollars, Quali5.com – Own A Keyword Forever, AntiSE, Serkai, Leather & Hide, GeoDig