We use cookies to give you the best experience possible. By continuing we’ll assume you’re on board with our cookie policy

See Pricing

What's Your Topic?

Hire a Professional Writer Now

The input space is limited by 250 symbols

What's Your Deadline?

Choose 3 Hours or More.
Back
2/4 steps

How Many Pages?

Back
3/4 steps

Sign Up and See Pricing

"You must agree to out terms of services and privacy policy"
Back
Get Offer

Internet technology assignment

Hire a Professional Writer Now

The input space is limited by 250 symbols

Deadline:2 days left
"You must agree to out terms of services and privacy policy"
Write my paper

Internet technology assignment

1.      Web-pages for public online ordering system:

Don't use plagiarized sources. Get Your Custom Essay on
Internet technology assignment
Just from $13,9/Page
Get custom paper

Here are the screen shots for the main pages on the online ordering of XYZ electronics products:

Home Page:

As shown above, the Home page contains a small animation of a computer Warehouse and product categories on the bar. Below a message is displayed in marquee format showing user about acceptance of credit card.

Few other main pages are as displayed below.

Desktop page:

Login Page:

User can login for the better services.

If he is new user, he can also sign-up to be member of XYZ electronics customer.

Peripherals Page:

This page shows the list of various peripherals. User can check the check box given in front of the product name. Total price is also displayed in red which is calculated dynamically, as the user ticks in the check box. When user clicks on the Deliver button, order page appears.

Order Page:

Here, User has to fill in the required details and then click on deliver button to get the order.

After clicking on Deliver button, information is verified and product is delivery is recorded and a thank you page appears.

Thank you page:

2.      Java script code to validate credit or debit card number:

<script type=”text/javascript”>

function validate()

{          if(document.myform.uname.value == “”)

            {

                        alert(“Please enter your name”);

                        return false;

            }

            if(document.myform.cardNo.value == “”)

            {

                        alert(“Please enter your credit card number”);

                        return false;

            }

            if(document.myform.address.value == “”)

            {

                        alert(“Please enter your address”);

                        return false;

            }

            var str = new String();

            str = document.myform.cardNo.value;

            var len = str.length

            if(len != 16)

            {

                        alert(“Credit  Card Number must be 16 digits long”);

                        return false;

            }

            for(var i=0;i<len;i++)

            {

                        if(isNaN(str.charAt(i)))

                        {

                                   alert(“Credit Card Number can contain only digits from 0 to 9”);

                                   return false;

                        }

            }

}

</script>

Testing of java script code:

3.      Snippet of Action script code:

<%

Response.Write(“<center><br><br><br>”)

Dim items

items = 0

Dim uname

uname = Session(“uname”)

Dim src

Dim MyConn

Set MyConn = Server.CreateObject(“ADODB.Connection”)

MyConn.Open “DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=” & Server.MapPath(“databases/data.mdb”)

Dim MyConn2

Set MyConn2 = Server.CreateObject(“ADODB.Connection”)

MyConn2.Open “DRIVER={Microsoft Access Driver (*.mdb)}; DBQ=” & Server.MapPath(“databases/pricelist.mdb”)

Dim SQL_query

Dim RS

Dim RS2

src = “L1”

SQL_query = “SELECT itemID FROM cart WHERE uname='” & uname & “‘ and itemID LIKE ‘”& src & “%'”

Set RS = MyConn.Execute(SQL_query)

      if not RS.EOF then

                  Response.Write(“<table width=’646′ height=’320′ border=’1′ align=’center’ cellpadding=’10’>”)

                  items = items + 1

                  Response.Write(“<tr>”)

                  Response.Write(“<td width=’181′ height=’170′><div align=’center’><img src=’images/laptop1.jpg’ width=’155′                                                     height=’160′ alt=’l1′ /></div></td>”)

                  Response.Write(“<td width=’340′ valign=’top’>”)

                  Response.Write(“<ul>”)

                  while not RS.EOF

                             SQL_query = “SELECT desc FROM pricelist WHERE icode='” & RS(“itemID”) & “‘”

                             Set RS2 = MyConn2.Execute(SQL_query)

                             Response.Write(“<b><li>” & RS2(“desc”) & “</b>”)

                             RS.MoveNext

                  wend

                  RS2.close

                  RS.close

                  Response.Write(“</ul>”)

                  Response.Write(“</td>”)

                  Response.Write(“<a name=’L1′></a>”)

                  Response.Write(“<td width=’94’><form id=’deliverL1′ name=’deliverL1′ method=’post’ action=’reqdelivery.asp’>”)

                  Response.Write(“<a href=””#L1″”><img src=’images/deliver.jpg’ alt=’Deliver’ onclick=’deliverL1.submit()’ border=0/></a>”)

                  Response.Write(“<p><input name=’source’ type=’hidden’ id=’source’ value=’L1′ /></p>”)

                  Response.Write(“<p>&nbsp;</p></form>”)

                  Response.Write(“<form id=’removeL1′ name=’removeL1′ method=’post’ action=’remove.asp’>”)

                  Response.Write(“<a href=””#L1″”><img src=’images/remove.jpg’ alt=’Remove from Cart’ onclick=’removeL1.submit()’ border=0 /></a>”)

                  Response.Write(“<p><input name=’source’ type=’hidden’ id=’source’ value=’L1′ /></p>”)

                  Response.Write(“</form></td>”)

                  Response.Write(“</tr>”)

      end if

src = “L2”

SQL_query = “SELECT itemID FROM cart WHERE uname='” & uname & “‘ and itemID LIKE ‘”& src & “%'”

Set RS = MyConn.Execute(SQL_query)

      if not RS.EOF then

                  if items = 0 then

                             Response.Write(“<table width=’646′ height=’320′ border=’1′ align=’center’ cellpadding=’10’>”)

                  end if

                  items = items + 1

                  Response.Write(“<tr>”)

                  Response.Write(“<td width=’181′ height=’170′><div align=’center’><img src=’images/laptop2.jpg’ width=’155′                                                     height=’160′ alt=’l1′ /></div></td>”)

                  Response.Write(“<td width=’340′ valign=’top’>”)

                  Response.Write(“<ul>”)

                  while not RS.EOF

                             SQL_query = “SELECT desc FROM pricelist WHERE icode='” & RS(“itemID”) & “‘”

                             Set RS2 = MyConn2.Execute(SQL_query)

                             Response.Write(“<b><li>” & RS2(“desc”) & “</b>”)

                             RS.MoveNext

                  wend

                  Response.Write(“</ul>”)

                  Response.Write(“<a name=’L2′></a>”)

                  Response.Write(“<td width=’94’><form id=’deliverL2′ name=’deliverL2′ method=’post’ action=’reqdelivery.asp’>”)

                  Response.Write(“<a href=””#L2″”><img src=’images/deliver.jpg’ alt=’Deliver’ onclick=’deliverL2.submit()’ border=0 /></a>”)

                  Response.Write(“<p><input name=’source’ type=’hidden’ id=’source’ value=’L2′ /></p>”)

                  Response.Write(“<p>&nbsp;</p></form>”)

                  Response.Write(“<form id=’removeL2′ name=’removeL2′ method=’post’ action=’remove.asp’>”)

                  Response.Write(“<a href=””#L2″”><img src=’images/remove.jpg’ alt=’Remove from Cart’ onclick=’removeL2.submit()’ border=0 /></a>”)

                  Response.Write(“<p><input name=’source’ type=’hidden’ id=’source’ value=’L2′ /></p>”)

                  Response.Write(“</form></td>”)

      end if

src = “D1”

SQL_query = “SELECT itemID FROM cart WHERE uname='” & uname & “‘ and itemID LIKE ‘”& src & “%'”

Set RS = MyConn.Execute(SQL_query)

      if not RS.EOF then

                  if items = 0 then

                             Response.Write(“<table width=’646′ height=’320′ border=’1′ align=’center’ cellpadding=’10’>”)

                  end if

                  items = items + 1

                  Response.Write(“<tr>”)

                  Response.Write(“<td width=’181′ height=’170′><div align=’center’><img src=’images/free-desktop-pc.jpg’ alt=’d1′ width=’181′ height=’122′ /></div></td>”)

                  Response.Write(“<td width=’340′ valign=’top’>”)

                  Response.Write(“<ul>”)

                  while not RS.EOF

                             SQL_query = “SELECT desc FROM pricelist WHERE icode='” & RS(“itemID”) & “‘”

                             Set RS2 = MyConn2.Execute(SQL_query)

                             Response.Write(“<b><li>” & RS2(“desc”) & “</b>”)

                             RS.MoveNext

                  wend

                  Response.Write(“</ul>”)

                  Response.Write(“<a name=’D1′></a>”)

                  Response.Write(“<td width=’94’><form id=’deliverD1′ name=’deliverD1′ method=’post’ action=’reqdelivery.asp’>”)

                  Response.Write(“<a href=””#D1″”><img src=’images/deliver.jpg’ alt=’Deliver’ onclick=’deliverD1.submit()’ border=0 /></a>”)

                  Response.Write(“<p><input name=’source’ type=’hidden’ id=’source’ value=’D1′ /></p>”)

                  Response.Write(“<p>&nbsp;</p></form>”)

                  Response.Write(“<form id=’removeD1′ name=’removeD1′ method=’post’ action=’remove.asp’>”)

                  Response.Write(“<a href=””#D1″”><img src=’images/remove.jpg’ alt=’Remove from Cart’ onclick=’removeD1.submit()’ border=0 /></a>”)

                  Response.Write(“<p><input name=’source’ type=’hidden’ id=’source’ value=’D1′ /></p>”)

                  Response.Write(“</form></td>”)

                  Response.Write(“</tr>”)

      end if

src = “D2”

SQL_query = “SELECT itemID FROM cart WHERE uname='” & uname & “‘ and itemID LIKE ‘”& src & “%'”

Set RS = MyConn.Execute(SQL_query)

      if not RS.EOF then

                  if items = 0 then

                             Response.Write(“<table width=’646′ height=’320′ border=’1′ align=’center’ cellpadding=’10’>”)

                  end if

                  items = items + 1

                  Response.Write(“<tr>”)

                  Response.Write(“<td width=’181′ height=’170′><div align=’center’><img src=’images/a1600n.jpg’ alt=’d2′ width=’198′ height=’146′ /></div></td>”)

                  Response.Write(“<td width=’340′ valign=’top’>”)

                  Response.Write(“<ul>”)

                  while not RS.EOF

                             SQL_query = “SELECT desc FROM pricelist WHERE icode='” & RS(“itemID”) & “‘”

                             Set RS2 = MyConn2.Execute(SQL_query)

                             Response.Write(“<b><li>” & RS2(“desc”) & “</b>”)

                             RS.MoveNext

                  wend

                  Response.Write(“</ul>”)

                  Response.Write(“<a name=’D2′></a>”)

                  Response.Write(“<td width=’94’><form id=’deliverD2′ name=’deliverD2′ method=’post’ action=’reqdelivery.asp’>”)

                  Response.Write(“<a href=””#D2″”><img src=’images/deliver.jpg’ alt=’Deliver’ onclick=’deliverD2.submit()’ border=0 /></a>”)

                  Response.Write(“<p><input name=’source’ type=’hidden’ id=’source’ value=’D2′ /></p>”)

                  Response.Write(“<p>&nbsp;</p></form>”)

                  Response.Write(“<form id=’removeD2′ name=’removeD2′ method=’post’ action=’remove.asp’>”)

                  Response.Write(“<a href=””#D2″”><img src=’images/remove.jpg’ alt=’Remove from Cart’ onclick=’removeD2.submit()’ border=0 /></a>”)

                  Response.Write(“<p><input name=’source’ type=’hidden’ id=’source’ value=’D2′ /></p>”)

                  Response.Write(“</form></td>”)

                  Response.Write(“</tr>”)

      end if

      if items = 0 then

                  Response.Write(“<font color=#ff0000><b><h2>No items to display</h2></b></font><br><br><br><br>”)

      else

                  Response.Write(“</table>”)

      end if

      Response.Write(“</center>”)

%>

4. COMMON OBJECT REQUEST BROKER ARCHITECTURE (CORBA):

CORBA is a specification that specifies how components can interact with each other over a network. It allows developers to define distributed component architectures without worrying about the underlying network communications and programming languages.

The language independence is achieved by the fact that components in CORBA are declared in language called Interface Definition Language (IDL). Developers can write the actual internal code of the components in a programming language of their choice, such as Java, C++ etc.

At the heart of CORBA is the evaluation of distributed components architecture, also called distributed objects architecture. This architecture extends the n-tier (also called multi-tier) client-server e-commerce applications to their logical conclusion.

            In another way, we can say that CORBA allows developers to create components, define their interfaces and then it takes care of the interaction between them. It takes upon itself the job of locating components/interfaces and invoking them as and when necessary.

            Various players in CORBA architecture are:

Object Request Broker: It is heart of distributed components architecture. ORB is actually software program that runs in the client as well as on the application server, where most of the components reside. It is responsible for making communication between various distributed objects possible.

Interface Definition Language: IDL specifies the interfaces between the various CORBA components. IDL ensures that CORBA components can interact with each other without regard to the programming language used.

Internet Inter-ORB Protocol (IIOP): CORBA ORBs communicate with each other using the IIOP. Basically, it is used for component-level communication between CORBA clients and CORBA servers.

REMOTE METHOD INVOCATION (RMI):

The Java programming language has in-built support for the distributed component-based computing model. This support is provided by RMI. It is the Java standard for distributing the components.

RMI allows components written in Java to communicate with other Java components that reside on different physical machines. For this purpose, RMI provides a set of Application Programming Interface (API) calls, as well as the basic infrastructure, similar to what CORBA’s ORB provides.

RMI and CORBA are remarkably similar in terms of concepts. RMI has two new types of components: stubs and skeletons. A stub is a client side component, which is a representation of the actual component on the server and executes on client machine. On the other hand, a skeleton is a server component. It has to deal with the fact that it is a remote component. That is, it has to take care of responding to other components that request for its services.

The beauty of this scheme is that a developer does not have to write the stub and skeleton interfaces. The Java environment generates it once the basic class is ready.

 For example, suppose there is a search class written in Java that allows the user to search for a specific record from the database. Then the developer has to simply write search class. A special compiler can generate the stub and skeleton interfaces for this class.

RMI is essentially the Java version of Remote Procedure Calls (RPCs). The basic infrastructure of an RMI-based method appears very similar to a RPC-based system.

WEB-SERVICES:

Web-services are nothing but the integration of various web-technologies and protocols to develop the web-based applications. Integrated web-based applications are XML, SOAP, WSDL and UDDI open standards. These web-applications are integrated over an Internet backbone. Web-services are sometimes also called as application services.

XML (Extensible Markup Language) is used to tag the data i.e. message between client and server is send using XML format. SOAP (Simple Object Access Protocol) is a protocol based on XML that allows applications to exchange information using HTTP.

WSDL (Web-service definition language) describes network services in XML format as a set of end points. Network services are described as a set of end-points operating on the messages which could be either document oriented or procedure oriented information.

UDDI (Universal Description Discovery and Integration) is a registry based on XML for businesses worldwide to get listed on the internet. This registry is platform independent.  UDDI is integrated with SOAP messages to provide access to WSDL.

Web-services allow organizations to communicate over the network without letting each other know about their IT systems. Since all communication is in XML, web-services can work on all operating systems and used by all programming languages. They do not require use of Browser or HTML.

Web-services share business logic; data and programmatic interface through network. They do not provide Graphical User Interface.

5. Comparisons

Point

CORBA

RMI

Standardization

CORBA is a standard. It is language independent.
RMI is part of java programming language itself. It completely depends upon Java.

    Underlying protocol

CORBA uses (Internet Inter-Object Request Broker Protocol) IIOP as its underlying protocol.
RMI uses the Java Remote Method Protocol as its underlying protocol in older versions. IIOP protocol is also used in newer versions.

Garbage Collection

Since, it is language independent, it does not attempt to perform general purpose distributed garbage collection.
Since, it is part of Java; It attempts to perform distributed garbage collection of remote server objects using the mechanism incorporated in the Java Virtual Machine (JVM).

Exception Handling

CORBA contains exception objects to handle exceptions. When any distributed object throws an exception object, the ORB automatically serializes and marshals it.
RMI allows throwing exceptions which are then serialized across the wire.

Language Independence

Since, CORBA is just a specification; various programming languages can be used to code these objects using ORB libraries.
RMI objects can only be coded in Java programming language because it relies heavily on Java Object Serialization.

         Parameter Passing
When passing parameters between client and remote server object, all interface types are passed by reference. All other objects are passed by value indicating highly complex data types.
When passing parameters between the client and the remote server object, all interfaces are passed by remote reference. All other objects are passed by value.

Object Implementation

Object Request Broker is responsible for locating an object implementation.
In the context of RMI, Java Virtual Machine is responsible for locating an object implementation.

Inheritance
CORBA supports multiple inheritance at the interface level.
RMI supports multiple inheritance at the interface level.

Transparency
CORBA provides Operating system transparency, Architecture transparency, Object Location transparency, protocol transparency, implementation transparency, Language transparency, Server transparency.
RMI provides operating system transparency, Object location transparency, implementation transparency, Architecture transparency etc. but it doesn’t provide Language and server transparency.

Advantages
·         You can reuse the CORBA components.

·         CORBA components do not need to be on the same physical machine or process.

·         Developers can define their own interfaces.

·         Various transparencies because of which client do not need to concern about internal details and implementation of system.

·         It is operating system and language independent.

·         Because of its simplicity and implementation, it leads to development of more robust, flexible and easily maintainable applications.

·         Since, it is multi threaded it allows parallel computing.

·         If the DBMS gets changed, only server needs to get recompiled.

·         It can move class implementations from client to server and vice-versa.

·         It can easily get connected to existing legacy systems.

Limitations

·         It is very complicated i.e. it includes a lot of complicated argument marshaling and de-marshalling. For example: If you have an application that is going to run in one process, using CORBA components entail a lot of overhead.

·         Because of its complexity, it is not recommended for Online Transaction Processing systems.

·         It works on Java only.

·         You need at least two sockets per connection.

·         Doesn’t work well when huge load comes on to the server.

·         Deploying an RMI connection requires additional network firewall configuration.

·         It uses TCP protocol but not UDP therefore it is not useful for heavier data transfer like video or audio transfers.

Point

CORBA

WEB-SERVICES

Underlying protocol

CORBA uses (Internet Inter-Object Request Broker Protocol) IIOP as its underlying protocol.
Web-services use Service oriented architecture; therefore it uses SOAP as its underlying network protocol. It uses simple XML-based protocols too.

Programming model

Programming model for CORBA is very complex as it is intended for Distributed applications.
Programming model is vast simplified relative to CORBA.

Service Description

Services are described using invoking remote methods using ORBS.
Services are described in terms of message accepted or generated.

Data Model
CORBA is a real object oriented component framework.
In Web-service, there is no notion of objects; they are centered on a message passing paradigm.

Type-checking

CORBA has got a standardized infrastructure support in terms of IDL, which is strongly typed.

Web-services don’t have any standardized infrastructure as such, only structure of SOAP messages is checked at run time and payload is only required to be a piece of well-formed XML.

Scalability and Reliability

CORBA achieves scalability and reliability by using its 3 features:

Portable object adapter, fault tolerant CORBA features and Load-balancing CORBA service.
Various components handle the issues of scalability and reliability in Web-services.

Location Transparency
Client application does not need to know whether object invoked is local or remote.
Here, Objects are accessed by using URLs which implicitly encode the location of services.

Error Handling
IDL exceptions are used for error handling in CORBA.
SOAP fault messages are used for error handling.

Security
CORBA provides a variety of security features like encryption, authentication, delegation etc.
It does not have any standardized security features but XML-signatures or SSL are used to provide security.

Advantages
·         You can reuse the CORBA components.

·         CORBA components do not need to be on the same physical machine or process.

·         Developers can define their own interfaces.

·         Various transparencies because of which client do not need to concern about internal details and implementation of system.

·         It is operating system and language independent.

·         Web-services are platform independent.

·         Provides interoperability by using UDDI mechanism as this mechanism is used for advertising the services.

·         They are deployed over standard internet technologies.

·         Since they use SOAP/HTTP, they do not require additional firewall configuration.

·         They are very useful in developing central repositories.

Limitations
·         It is very complicated i.e. it includes a lot of complicated argument marshaling and de-marshalling. For example: If you have an application that is going to run in one process, using CORBA components entail a lot of overhead.

·         Because of its complexity, it is not recommended for Online Transaction Processing systems.
·         Web services lack access from web-browser.

·         Web-services use plain text protocols that make requests larger than the other protocol. This extra size needs higher internet speed connections. This is an issue over slower speed connections.

·         Using web-services it is difficult to make long and steady connections like CORBA and RMI.

6. Recommendation:

After referring to all of above design & development options, it is recommended that Remote Method Invocation (RMI) is the best option to integrate the systems.

v  Following are the reasons for not selecting CORBA as the best option:

·         In the CORBA system, ORBs need to be stored on both client as well as on the server machine. Probability of a client having ORBs on his system is much less.

·         CORBA system may slow down the payment and order process of client because of its architectural complexity.

·         Since CORBA is a very complex architecture, its development is much complex too, which is very costly and makes you to think upon Return on Investment (ROI) analysis.

v  Following are the reasons for not selecting Web-Services as the best option:

·         Web-services are simple service-based architectures which mean they just accept the messages and generate the messages as and when required. In case of XYZ online shopping system such kind of structure is not required.

·         Since, web-services does not use a standard security mechanism, it may prove harmful for the customer. Since, personal information and credit or debit card details must be supplied in a very secure manner.

·         It uses XML based protocol which makes it difficult to integrate the systems.

v  Following are reasons to select the Remote Method Invocations (RMI)  as the best among the three:

·         Since, RMI is implemented in Java which is a portable language can run on any system including Windows, UNIX and others too.

·         RMI can also handle XML based applications because Java has the features to handle XML data.

·         RMI uses the tight security measures, which would help the company to keep the personal information of a customer safe.

·         RMI has the capability to implement a simple and robust application which can handle the operations of XYZ in a flexible and secure manner.

·         It is cheapest option because maintenance of a RMI system is easier than CORBA and Web-services. Company has this technology available too (as stated).

·         It provides better interfaces to provide user a good navigation tool.

Conclusion:

From the above study, it is concluded that the RMI is the better option to develop and integrate the system for XYZ Company than CORBA and Web-service architectures.

Reference List

Godbole, A. “Web Technologies.” Middleware and Component-based E-commerce Architectures, 2003, Tata MacGrawHill

 

Cite this Internet technology assignment

Internet technology assignment. (2016, Oct 24). Retrieved from https://graduateway.com/internet-technology-assignment/

Show less
  • Use multiple resourses when assembling your essay
  • Get help form professional writers when not sure you can do it yourself
  • Use Plagiarism Checker to double check your essay
  • Do not copy and paste free to download essays
Get plagiarism free essay

Search for essay samples now

Haven't found the Essay You Want?

Get my paper now

For Only $13.90/page