Should I use Java 2 Runtime Environ. or Should I use 1.1 Java Components in my Applet


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: Should I use Java 2 Runtime Environ. or Should I use 1.1 Java Components in my Applet

  1. #1
    Jasmin Guest

    Should I use Java 2 Runtime Environ. or Should I use 1.1 Java Components in my Applet


    Hi
    Should I use Java 2 Runtime Enironment so I can support Swing components
    or can I do the same functionality as far as JDBC:ODBC and SQL ....with
    for example 1.1.7 JDK ?
    The problem occured when I developed an JApplet which had the following criterias:
    1) it connects to the data source
    2) depending what you enter as Refresh rate.. I refresh your TextArea with
    new data from DB

    It is fairly simple for my first project but I realized that after I create
    JAR an after I uploaded HTML,JAR and all classes on my Web Server .. adn
    after I tested the applet on other clients .. well it takes at least 3-4
    minutes to load entire JAR and then it runs....

    See the problem ?

    Thank you for any response that might help me.

    Jasmin C.

  2. #2
    Interesting Guest

    Re: Should I use Java 2 Runtime Environ. or Should I use 1.1 Java Components in my Applet


    Do not tell me that you are not using java plug-in


    "Jasmin" <jasminc@juno.com> wrote:
    >
    >Hi
    >Should I use Java 2 Runtime Enironment so I can support Swing components
    >or can I do the same functionality as far as JDBC:ODBC and SQL ....with
    >for example 1.1.7 JDK ?
    >The problem occured when I developed an JApplet which had the following

    criterias:
    >1) it connects to the data source
    >2) depending what you enter as Refresh rate.. I refresh your TextArea with
    >new data from DB
    >
    >It is fairly simple for my first project but I realized that after I create
    >JAR an after I uploaded HTML,JAR and all classes on my Web Server .. adn
    >after I tested the applet on other clients .. well it takes at least 3-4
    >minutes to load entire JAR and then it runs....
    >
    >See the problem ?
    >
    >Thank you for any response that might help me.
    >
    >Jasmin C.



  3. #3
    Anubhav Guest

    Re: Should I use Java 2 Runtime Environ. or Should I use 1.1 Java Components in my Applet


    hi,
    If you connect database using an applet it will be real slow as compared
    to asp or any other language , but only for initialising the applet, and
    later (after applet is initialised )it will be more effective.
    Thats why jdbc is not that popular. But I am waiting for Higher Band Width,
    lets wait for it.
    This is the only solution i have presently.
    >
    >
    >"Jasmin" <jasminc@juno.com> wrote:
    >>
    >>Hi
    >>Should I use Java 2 Runtime Enironment so I can support Swing components
    >>or can I do the same functionality as far as JDBC:ODBC and SQL ....with
    >>for example 1.1.7 JDK ?
    >>The problem occured when I developed an JApplet which had the following

    >criterias:
    >>1) it connects to the data source
    >>2) depending what you enter as Refresh rate.. I refresh your TextArea with
    >>new data from DB
    >>
    >>It is fairly simple for my first project but I realized that after I create
    >>JAR an after I uploaded HTML,JAR and all classes on my Web Server .. adn
    >>after I tested the applet on other clients .. well it takes at least 3-4
    >>minutes to load entire JAR and then it runs....
    >>
    >>See the problem ?
    >>
    >>Thank you for any response that might help me.
    >>
    >>Jasmin C.

    >



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center