Difference bewteen thin client and thick client

Hi:
can someone explain the difference between the thin client app and thick client app?

Thin Client: Little to no logic on front end. Typically a 3 tier architecture. Example is a web browser
Thick Client: Typically a client-server type architecture where some business logic/processing occurs on the front end

Similar Messages

  • Difference between Thin Drivers and Thick Drivers

    hi all,
    can any one tell me the difference between Thin Drivers and Thick Drivers.
    regards
    ravi

    OCI is Oracle Call Interface. That's the lowest-level client API Oracle offers and the API that every thick client application eventually uses. For example, a C++ application using ADO would use the OLE DB driver which is itself written in OCI.
    From a deployment standpoint, the major difference is that the thin driver can be deployed to any machine that has Java installed. The OCI driver can only be deployed to machines that have the Oracle client installed.
    From a performance & functionality standpoint, there are features that only the OCI driver provides. Depending on the application, the OCI driver may also be faster.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Difference bewteen Single Client Access Name (SCAN) & Grid Naming Service

    Hi ,
    Whats the difference bewteen Single Client Access Name (SCAN) & Grid Naming Service in 11g RAC R2?
    Regards,
    Stephen

    Hi Stephen,
    There is a very good document about it (http://www.oracle.com/technetwork/products/clustering/overview/scan-129069.pdf).
    Best regards,
    Gennady

  • So what's the difference bewteen "packet data" and...

    just wanna know the difference between "packet data"and "highspeed GSM"while creating new access point in destination section.
    totally confused,any help should be appreciated.

    Essentially nothing.
    Depending on what you have your compiler strictness level set to, you can get it to generate a warning when you use an uninitialized variable.
    In Java, variables are assigned a default value dependent on type. All subclasses of Object are assigned a default type of null, and all primitive number data types are assigned a default value of 0.
    This differs from (for example) C, where variables are simply assigned a location in memory when they are declared, and the value of the variable is whatever was currently in that memory location when allocated. Using uninitialized variables in C is generally a big no-no.
    You'll find a lot of old-school C programmers who migrated to Java will initialize their variables :)
    Btw, this question probably belongs in another forum.

  • Heat difference bewteen 1.8 and 2.0 Macbooks?

    Is the difference betweeen the speeds of the Macbooks large enough to have an effect on how hot it the laptop will get? I've heard there have been complaints about heat and was wondering if all the people who were complaining had 2.0 Macbooks or if its all the models that are hot.
    Thanks in advance

    There should be no heat difference below 90% load. Above this the fans are on high anyways so I doubt you will see a difference. I was considering the same thing at one point, but I am fairly certain you will not see a difference between the two. The variation between 2.0 Macbook temps is also an indication that any small difference that there may possibly be, is much less than the diffrence of Apple properly building your particular notebook.
    Kalel

  • Difference between Costing Sheet and Assessment & Distribution Cycle.

    Hello Co Experts
    I need to understand the exact difference bewteen Costing sheet and Assessment dictribution cycles and their use for applying overhead cost to cost object especially Project WBS. Kind request to illustrate the preference of these two functionalityover each other with respect to business scenarios.
    Best Regards
    Adwait A Deshpande
    help.sap.com

    Hi Deshpande,
    The purpose of both are completely different.
    Assessment or Distribution cycles are used to transfer cost from the service/utility cost centers to the Production cost centers.
    Where as Costing sheet is a tool where you configure how system should calculate Production, Material ,Administration & Selling&Distribution in Product costing.
    Hope this helps.
    Thanks & Regards,
    Ravi Kumar

  • What is Thin and Thick Client ? Differences between the Two ? Which is Best

    Dear All,
    I like to develop both web-based and also standalone applications. i like to choose the best drivers for my applications. can anybody suggest which one to choose and what are the drawbacks in each driver ?
    Thanks,
    J.Kathir

    Dear All,
    I like to develop both web-based and
    h web-based and also standalone applications. i like
    to choose the best drivers for my applications. can
    anybody suggest which one to choose and what are the
    drawbacks in each driver ?I dont get what excatly you meaned by driver but basicaly a thin client means it only does the prescentation of data to its user and all the logics will be in a server. for every task it will connect to the server.
    In a Thick client it can do more processing and it will connect to the server only for the tasks that it cant perform with the data it has in the client.
    >
    Thanks,
    J.KathirHere is a general comparison between main features of thin/thick(fat) clients
    Both thin and thick clients has their own advantages and disadvantages. most of time one wins when other fails.
    1. Thin client extencvely uses the server to all its operations which will increace the network traffic and the load on the server. as a result the perfomance of the client will depend on the load and the resources available for the server
    2. But all the logic is in the server so if you are developing multiple clients for the same application (Ex:- Standallone app, Web client, Mobile clients......) you will not need to duplicate logic in each client.
    3. Fat clients reduce the load on server and less dependant on the server. but since they are fat they will take more processing power and memory on client computers.
    4. If you are developing multiple clients as menctioned in 2 you will need to duplicate the logics written the clients

  • JDBC thin and thick clients

    What is the difference between JDBC thin and JDBC thick clients and their usage ?

    hi,
    in sort tearms,
    Oracle has a thin client driver which mean you can connect to a oracle database without the Oracle client installed on your machine.
    Thick client would need the Oracle Client database drivers etc.. Drivers include JDBC-ODBC bridge drivers JDBC drivers depending on tns resolution.
    thanks

  • HFM Thin Client and Thick Client

    Hi
    can anyone tell me what is HFM thin client and thick client
    Thanks

    Thick client is the actual application client view. Most administrators limit that view to only them and provide a workspace (the thin client) as a method of accessing hfm. This is because more can be done in terms of metadata and security changes in the thick client than the thin client.

  • Differences between Oracle JDBC Thin and Thick Drivers

    If any body is looking for this information...
    ============================================================
    I have a question concerning the Oracle JDBC thin vs. thick drivers
    and how they might affect operations from an application perspective.
    We're in a Solais 8/Oracle 8.1.7.2 environment. We have several
    applications on several servers connecting to the Oracle database.
    For redundancy, we're looking into setting up TAF (transparent
    application failover). Currently, some of our apps use the Oracle
    <B>JDBC thin</B> drivers to talk to the database, with a connection
    string that like this:
    <B> jdbc:oracle:thin:@host:port:ORACLE_SID </B>
    In a disaster recovery mode, where we would switch the database
    from one server to another, the host name in the above string
    would become invalid. That means we have to shut down our application
    servers and restart them with an updated string.
    Using the Oracle <B>OCI (thick)</B> driver though, allows us to connect
    to a Net8 service instead of a specific server:
    <B> jdbc:oracle:oci8:@NET8_SERVICE_NAME </B>
    Coupled with the FAILOVER=ON option configured in Net8, it is
    then possible to direct a connection from the first server to
    the failover database on another server. This is exactly what
    we would like to do.
    My question is, from an application perspective, how is the Oracle
    thick driver different from the thin driver? If everything
    else is "equal" (i.e. the thick driver is compatible with the
    app servers) would there be something within the the thick/OCI
    driver that could limit functionality vs. the thin driver?
    My understand, which obviously is sketchy, is that the thick
    driver is a superset of the thin driver. If this is the case,
    and for example if all database connections were handled through
    a configuration file with the above OCI connection string, then
    theoretically the thick driver should work.
    ============================================================
    <B>
    In the case with the Oracle, they provide a thin driver that is a 100% Java driver for client-side use without the need of an Oracle installation (maybe that's why we need to input server name and port number of the database server). This is platform indipendent, and has good performance and some features.
    The OCI driver on the other hand is not java, require Oracle installation, platform dependent, performance is faster, and has a complete list of all the features.
    </B>
    ========================================================
    I hope this is what you expect.
    JDBC OCI client-side driver: This is a JDBC Type 2 driver that uses Java native methods to call entrypoints in an underlying C library. That C library, called OCI (Oracle Call Interface), interacts with an Oracle database. <B>The JDBC OCI driver requires an Oracle (7.3.4 or above) client installation (including SQL*Net v2.3 or above) and all other dependent files.</B> The use of native methods makes the JDBC OCI driver platform specific. Oracle supports Solaris, Windows, and many other platforms. This means that the Oracle JDBC OCI driver is not appropriate for Java applets, because it depends on a C library to be preinstalled.
    JDBC Thin client-side driver: This is a JDBC Type 4 driver that uses Java to connect directly to Oracle. It emulates Oracle's SQL*Net Net8 and TTC adapters using its own TCP/IP based Java socket implementation. <B>The JDBC Thin driver does not require Oracle client software to be installed, but does require the server to be configured with a TCP/IP listener. Because it is written entirely in Java, this driver is platform-independent.</B> The JDBC Thin driver can be downloaded into any browser as part of a Java application. (Note that if running in a client browser, that browser must allow the applet to open a Java socket connection back to the server.
    JDBC Thin server-side driver: This is another JDBC Type 4 driver that uses Java to connect directly to Oracle. This driver is used internally by the JServer within the Oracle server. This driver offers the same functionality as the client-side JDBC Thin driver (above), but runs inside an Oracle database and is used to access remote databases. Because it is written entirely in Java, this driver is platform-independent. There is no difference in your code between using the Thin driver from a client application or from inside a server.
    ======================================================
    How does one connect with the JDBC Thin Driver?
    The the JDBC thin driver provides the only way to access Oracle from the Web (applets). It is smaller and faster than the OCI drivers, and doesn't require a pre-installed version of the JDBC drivers.
    import java.sql.*;
    class dbAccess {
    public static void main (String args []) throws SQLException
    DriverManager.registerDriver (new oracle.jdbc.driver.OracleDriver());
    Connection conn = DriverManager.getConnection
    ("jdbc:oracle:thin:@qit-uq-cbiw:1526:orcl", "scott", "tiger");
    // @machineName:port:SID, userid, password
    Statement stmt = conn.createStatement();
    ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
    while (rset.next())
    System.out.println (rset.getString(1)); // Print col 1
    stmt.close();
    How does one connect with the JDBC OCI Driver?
    One must have Net8 (SQL*Net) installed and working before attempting to use one of the OCI drivers.
    import java.sql.*;
    class dbAccess {
    public static void main (String args []) throws SQLException
    try {
    Class.forName ("oracle.jdbc.driver.OracleDriver");
    } catch (ClassNotFoundException e) {
    e.printStackTrace();
    Connection conn = DriverManager.getConnection
    ("jdbc:oracle:oci8:@qit-uq-cbiw_orcl", "scott", "tiger");
    // or oci7 @TNSNames_Entry, userid, password
    Statement stmt = conn.createStatement();
    ResultSet rset = stmt.executeQuery("select BANNER from SYS.V_$VERSION");
    while (rset.next())
    System.out.println (rset.getString(1)); // Print col 1
    stmt.close();
    =================================================================

    Wow, not sure what your question was, but there sure was a lot of information there...
    There really is only one case where failover occurs, and it would not normally be in a disaster recovery situation, where you define disaster recovery as the obliteration of your current server farm, network and concievably the operational support staff. This would require a rebuild of your server, network etc and isn't something done with software.
    Fail over is normally used for high availablity that would take over in case of hardware server failure, or when your support staff wants to do maintenance on the primary server.
    Using the thin and thick driver should have ZERO affect on a failover. Transparent failover will make the secondary server the same IP as the primary, therefore the hostname will still point to the appropriate server. If you are doing this wrong, then you will have to point all your applications to a new IP address. This should be something that you tell your management is UNACCEPTABLE in a fail-over situation, since it is almost sure to fail to fail-over.
    You point out that you are providing the TNSNAME, rather than the HOSTNAME when using the thick driver. That's true within your application, but that name is resolved to either a HOSTNAME, or IP ADDRESS before it is sent to the appropriate Oracle server/instance. It is resolved using either a NAME server (same as DNS server but for Oracle), or by looking at a TNSNAMES file. Since the TNSNAMES files profilerate like rabbits within an organization you don't want a fail over that will make you find and switch all the entries, so you must come up with a fail over that does not require it.
    So, the application should not be concerned with either the hostname, or the IP address changing during fail over. That makes use of the thin or thick client acceptable for fail over.
    Don't know if this will help, but this shows the communication points.
    THIN DRIVER
    client --> dns --> server/port --> SID
    THICK DRIVER
    client --> names server --> dns --> server/port --> SID
    client --> tnsnames     --> dns --> server/port --> SID

  • THICK CLIENTS & THIN CLIENTS

    Can any body please tell me in detail what is the difference between a Thick client and a Thin client. Also tell me using either of these in specific occassions.

    And it's normally called a 'Rich Client' not 'Thick Client'.No, "rich client" is a newer developer.
    s/developer/development/I think it's more than a when Sales/Marketing people wanted to promote thin client solutions (during the fashionable thin 90's) they used devisive language of (Thick/Fat) against the alternative traditional Client Server solutions even though these could be Rich or Thin. I remember when Applets where considered thin, then it had to be Web-Pages to be really Thin and now that things have gone full circle with the introduction of things like AJAX and WebStart they use the old^Wnew terminology, or Rich Clients to distance it from the negitive associations of Thick and Fat.
    To me, fashions come and go but they will always be Thin or Rich :)

  • Diff between Thin client and Rich client

    Hi Everyone,
              Can someone give me a clear picture of the what is the diff between Thin client and Rich client.
    Thanks,
    Krishna

    Hi,
    thick client (rich client) has/stores all the data inside itself
    so it can do application processing without the server with data
    thin client uses resources from host computer (from server)
    and wihtout that you are not able to work with that kind of client
    does that answer your question ?
    Regards,
    michal

  • Rich client and thin client

    Hello experts,
    Rich contents are data manager, console, import manager and syndicator GUI clients
    thin contents are portal way of looking mdm using iviews.
    is this true??
    Regards
    Eva M

    Hi Eva,
    Good Day !
    You are right .
    A thing client (generally a software application/portal) depends primarily on a central server ( MDM server in this case) .It will drive communicating inputs from user to server and delivering back outputs from server to the user.Thin clients are independent of the machine you are using .
    Eg:Portal
    A thick client passes on data from an MDM user to Server . Such clients are generally used for performing data storage and processing activities directly at server level.Thiick clients need dedicated installations of GUIs and are machine dependant.
    Eg:data manager, console, import manager and syndicator GUI clients
    Hope this clarifies your query.
    Regards,
    Vinay M.S

  • Database connection encryption and integrity with ColdFusion and Oracle thin client

    As ColdFusion datasource we are using the Oracle thin client to  connect with the database. So, basically we are using a JDBC URL such as  jdbc:oracle:thin:@... and as Driver Class oracle.jdbc.OracleDriver. This works successfully however we would like to set encryption and  integrity parameters as well. In Java this is done similarly by setting a  Properties object prior to getting a connection as follows:
    Properties prop = new Properties();
    prop.put("oracle.net.encryption_client", "REQUIRED");
    prop.put("oracle.net.encryption_types_client", "( DES40 )");
    prop.put("oracle.net.crypto_checksum_client", "REQUESTED");
    prop.put("oracle.net.crypto_checksum_types_client", "( MD5 )");
    OracleDataSource ods = new OracleDataSource();
    ods.setProperties(prop);
    ods.setURL("jdbc:oracle:thin:@localhost:1521:main");
    Connection conn = ods.getConnection();
    Is there a way that I can pass these parameters to the ColdFusion  datasource. Ideally, I would love to do this centrally in such way that a  change to all the cfquery or cfstoredproc is not needed.
    I also know that in application servers such as Oracle AS there is an  option when creating a datasource which says "Add Properties". In there  you can add such properties. So, I was thinking of maybe creating a  JNDI DS in the app. server and then magically connecting to it but this  may have some impacts on the app.
    Besides this I was also thinking of communicating with the CF  datasource through the CF admin API (cfide.adminapi.administrator) and  also the option of extending the Oracle driver so that when CF connects  with it these params are already set.
    I would love to have your professional opinion and suggestions on this.

    I believe the thin driver actually needs the IP address (not the DNS name). Also, is "java" the name of the Oracle instance to which you are trying to connect?
    Try the following:String driver = "jdbc:oracle:thin";
    String dbIP = "W2RZ1NXG01's IP address";
    String dbPort = "1530";
    String dbSid = "java";
    String dbUser = "Admin";
    String dbPswd = "apassword";
    String cnctStr = driver + ":@" + dbIP + ":" + port + ":" + dbSid;
    try
        Class.forName("oracle.jdbc.driver.OracleDriver");
        con = DriverManager.getConnection( cnctStr, dbUser, dbPswd );
        stmt = con.createStatement();
        stmt.executeUpdate(createString);
        stmt.close();
        con.close();
    catch(SQLException ex)
        System.err.println( "The following SQLException occurred: " + ex );
        System.err.println( "Message: " + ex.getMessage() );

  • What files do I need to download iPhone photos to a thin client (HP)? Apple Mobile Support gives 4 dll files to enable the iPhone to be detected and charged but the thin client doesn't see the camera or hard drive.

    The iTunes Installation files include 4 driver dlls that I can install on a Windows thin client to enable the iPhone to be charged.
    The iPhone hard drive or photos are not detected.  I guess I need scanner driver support to cope with the camera.
    Can anyone tell me which files from the iTune installation set are needed.
    It is not practical (or even possible?) to install the whole iTunes package.
    I've seen this question asked by a lot of people but never seen an answer. 
    Please, can someone help... 

    Thanks for the reply. 
    A thin client is used to connect to a Terminal Server, or in my customer's case, a Citrix Server.  I need the thin client to see the iPhone as a camera and pass it to the Citrix Client so the photos can THEN be either stored on a network storage device, or e-mailed.
    Because the thin client doesn't even SEE a camera (i.e. the iPhone) it won't be able to connect to iCloud to do anything useful. 
    I think the question I should be asking, is how do I give the thin client Camera Support.
    I've just seen a 2008 forum comment that said the iPhone DOESN'T handle photos through iTunes, but the PC (Scanner support) or MAC (iPhoto) handles them directly.  I should be putting the question to HP.
    This is still a good place for THIS question, because I've seen so many iPhone users asking it...
    If I get a satisfactory answer I'll post it back here.

Maybe you are looking for