+

WO2000062161A2 - Procede et systeme de desserte d'application logicielles - Google Patents

Procede et systeme de desserte d'application logicielles Download PDF

Info

Publication number
WO2000062161A2
WO2000062161A2 PCT/US2000/009833 US0009833W WO0062161A2 WO 2000062161 A2 WO2000062161 A2 WO 2000062161A2 US 0009833 W US0009833 W US 0009833W WO 0062161 A2 WO0062161 A2 WO 0062161A2
Authority
WO
WIPO (PCT)
Prior art keywords
application
target computer
server system
server
computer
Prior art date
Application number
PCT/US2000/009833
Other languages
English (en)
Other versions
WO2000062161A3 (fr
Inventor
David M. Greschler
Owen Mysliwy
Stuart Schaefer
Original Assignee
Softwarewow.Com, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Softwarewow.Com, Inc. filed Critical Softwarewow.Com, Inc.
Priority to AU42361/00A priority Critical patent/AU4236100A/en
Publication of WO2000062161A2 publication Critical patent/WO2000062161A2/fr
Publication of WO2000062161A3 publication Critical patent/WO2000062161A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating

Definitions

  • a web-based software-sales institution can utilize the Internet, or other public network, to allow customers to "test-drive" the programs, and thereby increase sales.
  • a second justification for deployment arises in the thin- client/network-computer model where the code required for the application- functionality and user data reside on the server. In this situation, when required at the thin client, the application code is provided by the server on an as-needed basis.
  • These servers can even be off-site in an application service provider (ASP) environment.
  • ASP application service provider
  • Another justification surrounds the possibility to "rent" programs to users.
  • a large number of potential users may have only hmited requirements for certain classes of application programs. Their individual requirements may not justify investment in the typically expensive programs or not justify the costs of client installation. The thought here is to enable these users to rent access to the application programs, preferably via the Internet, to generate new revenue streams for the application software companies.
  • the selling institution may allow the potential owner to download a trial- version of the program.
  • This version may have reduced capabilities and/or a limited lifetime, where the program is disabled after it has been invoked a set number of times, or after a specified date.
  • This process is complex, often requiring a multi-step process in which the user must accept the download, pick a save-as location, watch the download, quit the browser, find the file on the hard drive, and run an installer, for example.
  • Another technique is to extend the potential purchaser's browser in some fashion using, for example, a Java applet. This approach, however, shares the problems discussed previously relative to ActiveX and Java.
  • the present method and system are directed to serving applications over a computer network from an application server system to a target computer.
  • a helper application is provided that handles client configuration to facilitate communications.
  • standard networking protocols can be used.
  • the invention features a method for serving applications over a computer network from an application server system to a target computer.
  • the method includes the target computer signaling the server system with a request for an application.
  • the server system responds to the request by transferring an application descriptor to the target computer.
  • the application descriptor is read by a helper application executing on the target computer.
  • the helper application controls the target computer to execute the application, which resides on the server system.
  • the target computer signals the server system with the request for the application by user selection of the link, which is displayed by a browser and associated with the application.
  • the application link contains an application identifier that identifies the requested application to the server system and may further contain a session ID, a user I.D, and a subscribing institution ID.
  • activating this application link triggers the downloading of the application descriptor from the server system to the target computer.
  • the application descriptor is encrypted prior to transmission.
  • the helper application is invoked in response to receipt of the application descriptor on the target computer. Thereafter, transaction modes may be set and advertisements served to the target computer.
  • the invention can also be characterized in the context of an application serving system that operates across a computer network.
  • the system comprises a target computer that requests an application.
  • a server system is provided that responds to the request by transferring an application descriptor to the client computer.
  • a helper process executing on the target computer reads this application descriptor and controls the target computer to execute the application, which resides on the application server system.
  • Fig. 1 is a schematic illustration showing the application serving system and specifically the interaction between the target client computer, the host Web server computer of the third-party subscribing institution, and the server system, according to the present invention
  • Fig. 2 is a flow diagram illustrating the method by which the serving of applications to the target computer is initiated at the third-party subscribing institution according to the present invention
  • Fig. 3 is a flow diagram illustrating the steps performed by the server system when the target computer requests an application
  • Fig. 4 is a flow diagram showing the launch process for the helper application, or software player, on the target client computer;
  • Figs. 5 A and 5B are flow diagrams showing the application launch process that is performed on the target client computer;
  • Figs. 6A-6C are flow diagrams showing the steps associated with the application monitoring process according to the present invention.
  • Fig. 7 is a flow diagram illustrating the application shutdown process according to the present invention.
  • Fig. 1 shows an application serving system 100, which has been constructed according to the principles of the present invention.
  • the application serving system 100 comprises the user, target client computer 110 that connects to a server system 112 and subscribing institution host Web Server 130, over a network 114.
  • Client computer 110, Web server 130, and server system 112 implement a network protocol layer to communicate across the network.
  • network 114 is the Internet, or other public or private network
  • the network protocol layers are TCP/TP and NetBios.
  • Other network configurations and network protocols layers could be implemented in place or in addition to those associated with the Internet such as those provided in other public or private networks and internetwork systems.
  • the target, client computer 110 is a PC computer in one implementation. It operates Microsoft Windows 95/98/NT/2000/CE operating system or other OS providing compatible API's (application programming interfaces), on an Intel processor/TJBM-compatible hardware platform.
  • Other alternatives are possible such as open source operating system platforms, such as Linux, or Apple MAC OS's or other operating systems that provide the API support for these operating systems.
  • Still further alternatives include embedded OS platforms such as Windows CE and Palm OS's, or similar reduced code-footprint systems.
  • the target computer 110 preferably has preinstalled application programs.
  • a browser 134 such as the ubiquitous Netscape Navigator or Microsoft Explorer browsers, is installed.
  • the target computer also preferably has a helper application or software player 132.
  • Such pre- installation can be performed typically at a website hosted by the institution that operates the server system 112 or also the subscribing institution 130.
  • the subscribing institution which maintains the host web server 130, is typically a third party relative to the institution, which maintains the server system 112 in one anticipated business model.
  • the subscribing institution has a requirement, or desires to provide, application programs and the related functionality to the user at the target computer 110, but, rather than providing this functionality itself, the subscribing institution outsources this to the institution operating the server system 112. Nonetheless, the subscribing institution typically has an Internet presence. Specifically, it typically maintains a website/websites that offer the application programs to users.
  • the server system 112 is maintained by an institution that provides application programs to users as a paid service to subscribing institutions. Nonetheless, it should be appreciated that the technology of the present invention also has applicability to the business model where the server system 112 and host Web server 120 are maintained by the same institution. In this context, the institution does not wish to out-source the work associated with the serving of the applications, but wishes to provide this functionality through in-house expertise.
  • the service institution's server system 112 maintains a log-in database 116, a customer database 118, an application database 120, and a current sessions database 122.
  • the server system additionally executes a session ID generator 124, a load balancing process 126, and an encryption process 128.
  • Fig. 2 shows the steps performed by or at the target computer 110 to initiate the serving of an application from the server system 112.
  • a user at the target computer identifies a desired application to the target computer 110 in step 210.
  • the browser 134 is executing on the target computer 110 and a link is displayed in the browser window. This link is identified and/or associated with the application that the user desires to execute on the target computer.
  • the user operating a graphical pointing device, such as a mouse, controls the target computer's graphical user interface to select or "click-on" the link for the desired application.
  • Selection of the link in step 210 causes the browser 134 to interrogate the target computer's operating system to determine whether the appropriate software player (SWP) has been installed on the target computer in step 212.
  • This interrogation is performed in one embodiment by an application programming interface (API) call to check the operating system registry.
  • API application programming interface
  • Applets, ActiveX, or scripting are other modalities for performing the interrogation.
  • this installation process comprises either pointing the browser 134, or a new instantiation of the browser, with a new universal resource locator (URL), to website that supports the installation of the software player through a download, for example.
  • URL universal resource locator
  • the install/download is simplified for ease of operation.
  • a Java applet is used that allows installation and writing to the drive— if permission is provided.
  • a download bar is displayed on the browser screen.
  • the browser 134 is pointed with a
  • the URL link contains: 1) a unique identifier, or number, associated by the server system 112 with the application requested (Titleld); 2) a unique session ID (SID); and 3) an identifier that identifies the subscribing institution (Sublnstld).
  • the subscribing institution is the company that operates the host Web server computer 130, which served the web page that originally contained the link associated with the application that was desired by the user of the target computer 110.
  • the SID is a unique session ID that is specific to the link and the specific session.
  • a session ID that served as part of the original link provides a token from the web site that tells indicates that the subscribing institution has authenticated this specific session. This is important for the rental/subscription model where they will be authenticating users with credit cards or user names and passwords.
  • Fig. 3 shows the steps performed by the server system 112 when the target computer 110 requests an application by transmitting the URL containing the SID, Titleld, and Sublnstld to the server system 112 over the network 114.
  • the server system 112 receives the URL, SID, Titleld, and Sublnstld.
  • the server system then accesses the log-in database 116 to verify that: 1) the user at the target computer 110 is a valid user by reference to the session Id field (SID); and 2) the subscribing institution is a currently valid subscribing institution by reference to the Sublnstld field in step 312. If either the user or subscribing institution is invalid (step 314), an error is returned to the target computer 110 in the step 316 by the server system 112.
  • the server system 112 then proceeds to construct an application descriptor or data file that will coordinate the operation of the target computer 110 and the server system 112 across the network 114.
  • the application descriptor is a file that is named with a " .WOW" suffix, which is the MIME type.
  • step 318 the server system 112 accesses the customer database 118 using the SID to obtain information regarding the session.
  • the application database 120 is accessed. This contains information concerning the application, which was requested by the user.
  • the application database 120 contains information such as minimum system requirements (RAM, processing power, etc.) that are required by the application on the target computer 110 and the application's media weight or processing requirements on the server system 112 associated with each instantiation.
  • the load balancing process 126 is executed.
  • the server system 112 selects a host computer within the server system that will be primarily responsible for serving the application over the network 114 to the target computer 110.
  • the server system comprises multiple host Web and associated application servers.
  • the selected host computer is co-located with the other host computers in one implementation; alternatively, components or servers of the server system are located in a server farm and/or geographically local to the target computer 110.
  • the load balancing process selects the host computer based on geographic proximity, in addition to load, to reduce latency.
  • the load balancing checks the current session's database 122 to determine which host server in the server system 112 has the least load.
  • the list of servers serving the specific application is part of the title's application description. Determination of which server to use is based on the number of concurrent connections to each server and the media weight of each application and also the user's physical geographic location based on the IP address.
  • the current sessions database 122 is updated in step 324 with the current session being added. Specifically, the session ID, the user's IP (internet protocol) address, the application title, the media weight, and the server assigned to the session is added.
  • This database is used by the load balancing process 126, and by a watch dog process that watches the connections to each host server in the server system, to verify that all connections are from authorized users.
  • step 326 the application descriptor is encrypted.
  • this application descriptor comprises the host address of the host computer of the server system 112, which was assigned by the load balancing process 126 along with a session ID assigned as part of the update of the current session database 122.
  • the application descriptor is sent to the target computer 110 in step 328.
  • Fig. 4 shows the launch process for the helper application or software player 132.
  • the client Upon receiving the .WOW application descriptor file, the client launches the software player 132 in step 409. This is a helper application that performs the bulk of the client-side application management.
  • the receipt of the .WOW descriptor file automatically launches the software player. This is accomplished by configuration of MIME types during the software player's initial installation. In the Windows 95 operating system, MIME types are set in the registry, associating files with a specified suffix, here: WOW, that are to be opened with the software player 132.
  • the Buddy API Xtra (a library of calls employed by programmers of Macromedia Director) is used to access Windows API functions. Specifically, the initial writing to the registry is done with the baWriteRegNumber and baWriteRegString commands in Buddy API.
  • the registration status of the software player 132 with respect to the server system 112, or institution operating the system is determined. If it has not been registered and/or properly licensed, a registration box is displayed on the graphical user interface of the target computer 110 in step 412. The user is either requested or required to complete the registration information box, depending on the implementation. Once completed, the registration information is sent, in step 414, to the server system 112 over network 114.
  • firewall proxy information dialog box is displayed in step 418, and the user is requested to complete it on the target computer 110. Once completed, the proxy information is updated in step 420.
  • step 422 the status of the application descriptor, or WOW file is interrogated in step 422. If no application descriptor file is detected, a dialog is generated in step 424, on the target computer 110 for the user. The user is requested to enter a partner or subscribing institution. If it is determined that no institution has been entered in step 426, the process aborts. However, if a subscribing institution was entered, the process similarly aborts in step 430, but also points the browser 134 to the Web page for the subscribing institution in step 432.
  • step 434 it is interrogated as to whether the client is monitoring a similar process, i.e., the software player 132 is currently running on the client. If it is not running, the SWP window is created in step 436. Depending on the run mode, the window is either hidden or visible on the client interface.
  • step 438 any system clean-up is performed. Generally, the operating system registry is written to when applications 133 are run. The software player tracks those modifications, and any registry changes; these changes are undone when the application 133 and software player 132 are quit. However, if the software player 132 was terminated unexpectedly during its last operation, the registry clean-up may not have been performed. If not, the clean-up occurs in this step. Specifically, any modified registry settings are returned, icons are removed, folders in any disk drive are removed, and any new copies of applications on the desktop are removed. Next, the player is set up on the OS tray.
  • step 444 If it was determined that the SWP is currently monitoring a process and thus invoked, in step 444, the status of the target computer operating system is interrogated in step 444. Iftoo many apphcations are currently running, a dialog is generated notifying the user in step 446 and the process aborts in step 448. However, if there is sufficient resources to run the application, the new launch application process is started in step 450.
  • Figs. 5A and 5B show the application launch process.
  • the software player 132 reads and decrypts the incoming application descriptor WOW file.
  • the program uses the baCommandArgs command in the Buddy API.
  • the decryption of the commands is done via the baDecryptText command in the Buddy API.
  • the software player 132 checks to see if this is the first time it has been run on the client computer 110 by checking the computer's internal settings to see if a unique ID has been written to the settings. This is done via the baReadRegString command in Buddy API. If it finds the unique ID, it continues. If it does not find a unique ID, it asks the user for personal information that will be collected for a User Database, in one exemplary implementation.
  • step 510 It then creates a WOW data struct in step 510.
  • the version of the application descriptor is then compared to the version of the software player 132 in step 512 to ensure compatibility. If there is no compatibility, a dialog is displayed in step 514 asking the user if they wish to upgrade to a new software player. If the user agrees to upgrade, the new dynamic link libraries (.DLL files) are downloaded from the server system 112 in step 516. The software player unloads the current dynamic link libraries and updates the DLL's in step 516.
  • step 514 the process aborts in step 518, while simultaneously pointing the browser 134 with an upgrade URL to a site hosted by the server system 112 or hosted by another server in step 520.
  • step 518 the application requirements contained in the application description are compared to the target computer's configuration in step 522. If there are inadequate resources, the process aborts in step 524. Additionally, the browser 134 is pointed toward a web page hosted by the server system providing for maintenance. Specifically, the maintenance URL is passed to the browser in step 526. For example, a minimum or maximum screen depth, resolution, RAM requirements, processor requirements, sound board requirements, and video board requirements are assessed.
  • baVersion("os) baVersion("qt)
  • baVersion(qt3) baScreenInfo("height")
  • baScreenInfo("width) baScreenInfo("depth”).
  • a message is sent from the target client computer 110 to the server system over the network 114 in step 528.
  • the message contains the session ID, which was just received from the server system in the application descriptor file.
  • a start request message is sent to the server system. The receipt of the session ID identifies the session and implicitly notifies the server system 112 that the target computer has successfully decrypted the application descriptor file, which had been previously sent. The start request indicates that the target client computer is now ready to begin to execute the requested application.
  • the software player 132 preferably determines, via the application descriptor, the transaction mode being used. This will impact the appearance of the player 134 on the screen or GUI of the computer 110. For example, if the application descriptor identifies itself as an advertisement-based transaction (noted as an "a" in the Application Descriptor), then the software player 132 will respond by positioning itself at the top level of the screen depth and begin to request advertisements from an advertisement server, within the server system 112, over the network 114. Conversely, if the application descriptor identifies itself as a subscription-based (noted as an "s" in the application descriptor), the software player 132 will hide itself, but continue to execute in the background. To hide itself the program uses the baWindowState command in Buddy API. The ads are obtains through hypertext transfer protocol (http) calls.
  • http hypertext transfer protocol
  • step 530 the target client computer 112 then waits for a start request acknowledgment from the server system 112. If no acknowledgment is received after a predetermined time period, a dialog is displayed on the target client computer 110 to notify the user that the server system is currently unavailable in step 532.
  • a proxy socket is opened in the target computer 110 and the application server address is passed to the proxy in step 536.
  • the software player 132 determines if any files are required from the server system 112 to continue the launch process. If additional files are required, they can be obtained by initiating a remote drive mounting process in step 540. Alternatively, the files can be obtained using a local file installation and replace process in step 542. Additionally, both processes could be used if multiple files are required.
  • Certain applications require specific files at specific locations. For example, certain anti-virus programs require virus definitions to exist at specific path. Such hard coded path requirements are addressed in this initial configurations check. A file check is performed and any required files are shipped to the client computer before the application is launched.
  • the target client computer 110 With the remote drive mounting and possibly local file installation/replace, the target client computer 110 now has access to the files and specifically the code required to invoke the selected application.
  • the directory is set to the local or remote drive and the run command is issued to the host server. In one embodiment, this occurs on port 139, the SMB port, from the perspective of the application.
  • standard Windows NT remote networking methods are used to attach to the server's directory using the Net Use command, which is part of the Windows Networking.
  • Windows 95 computers need to have the name of the server they are attaching to in a file in the Windows directory called LMHOST; the software player 132 writes the name of the server to the LMHOST file using the Filel/O command in Macromedia Director.
  • the software player 132 then waits for the application window and the update of the stream display in step 548.
  • the window status is acquired by reference to the operating system application programming interface. In the preferred embodiment, where it is operating on a Windows OS platform, the window status is obtained via the WIN API in step 550.
  • the stream data size is obtained from the proxy application in step 552.
  • step 554 it is interrogated as to whether or not the application window has opened. Until the window opens, the host server in the server system 112 is periodically pinged. The window timeout is reset as many as three times and as long as the server is responsive to the ping in step 558. If there is no server response to the ping as determined in step 556, the user is notified via the dialog in step 560 and the program aborts in step 562.
  • step 554 the user interface elements are activated that are specific to the application in step 564.
  • the size and position of the software player and application windows are then set in step 566.
  • step 568 the process proceeds to an application monitoring in step 568.
  • Fig. 6A illustrates the steps associated with application window monitor process and the tracking pulse process.
  • the client computer multitasks to also monitor the operation of the application.
  • One of the processes is the application window monitor process 610.
  • the application window monitor process 610 periodically makes API calls to determine whether or not the application's window is still open in step 612. If the window is open, it continues to maintain and/or set the position and layer of the windows of the application 133 and the software player 132 with respect to each other in step 614 according to the transaction mode. However, if the application window monitor process 610 determines that the application window has closed, the software player 132 begins the execution of a shutdown process 616.
  • the tracking pulse process 618 periodically sends a pulse or a ping to the host server of the server system 112 in step 620. If it is determined that no pulse has been received in step 622, the target client computer 110 pings the host server of the server system in step 624. Based on the status of the ping, if it is determined that there is no connection to the server, a dialog is generated in step 626 and there is a forced shutdown of the application process in step 628, and again, the shutdown process is activated 616. If the ping is successfully sent to the server, but no response is received, a dialog is generated in step 628. Again, a "no response" dialog is generated in step 630 and the shut down process is activated in step 616.
  • tracking is not provided by sending pulses; instead, the application server monitors socket connections to determine if connections are still active. From the client side, instead of the server telling the client to shut down, the client gets its "total time to run" as part of the .wow file and begins counting down — and eventually shuts down — once it hits zero time.
  • step 622 if it is determined that the pulse is received in step 622, the message is analyzed. If it is determined that the message is to turn off the application in step 632, the application process is terminated in step 628 and the shut down process is activated, step 616.
  • step 634 If the message returned that the application must be teirninated within n minutes, a dialog is generated in step 634, notifying the user of the remaining minutes of access to the application. A countdown timer is started in step 636. Finally, if the message returned is an all clear or o.k. message in step 632, process returns.
  • Fig. 6B shows the advertisement update process, net traffic monitoring process, and countdown timer process, which are additionally performed as part of the application monitoring.
  • the ad update process periodically updates the ads displayed on the software player and any URL's required for the ad server in step 640. It then returns to the run mode of the ad process in step 642.
  • the software player will maintain a +1 depth relationship with the application's window. This means that if the application 133 is brought to the front, the software player 132 will place itself in front of the application 133 so the application cannot hide the advertisements being served. If a different application or window, i.e., one not being hosted by the server system 112, is brought to the front, the software player 132 will not obscure the application or window. It will maintain its +1 depth relation to the application 133. This is accomplished via the baWindowDepth command in Buddy API. Also, the player is monitored so that it is not moved off the screen. Step 644 monitors network activity and notifies the net traffic monitoring process in step 646. This allows the application monitor to determine if there are any problems associated with high traffic, which would impact the operation of the application.
  • step 648 the display countdown timer is updated. This countdown timer notifies the user as to the time remaining in which the application is available. This is most relevant where the user has, for example, "rented" the application for a fixed period of time as indicated by the transaction mode.
  • the countdown timer updates the countdown timer process 650 so that a shut down process is automatically activated when the timer has timed-out.
  • Fig. 6C illustrates event handling process 652 of the application monitoring processes. Specifically, if the bookmark is selected in step 654, the URL of the third-party application hosting institution and its server system 112 is added to the start menu folder of the browser 132.
  • Quick Launch instead of adding it to the start menu folder system, it gets book-marked as part of a screen in the player — the one that comes up if you click on Quick Launch. It remembers the location from where you initially clicked, thus guaranteeing the web site that they will still get ad revenue and a follow-up page each time the user clicks on the Quick Launch bookmark.
  • a help file is displayed.
  • the browser 134 is pointed to a URL of a help file server in step 658.
  • the third party home is selected in step 660, the browser is pointed to the URL or a specified URL of the subscribing institution in step 662.
  • the home button is selected in step 664, the browser 134 is pointed to the home page of the third-party application hosting system in step 666.
  • the ad which is displayed by the player, is selected in step 668, the browser is pointed to the URL of the advertising company in step 670.
  • the quit button is selected in step 672, the application is forced to terminate in step 674 and the shutdown process is started in step 676.
  • Fig. 7 is a flow diagram illustrating the apphcation shutdown process. Specifically, if the application 133 is desired to be shutdown or quit in step 710, a shutdown pulse or signal is sent from the client computer 110 to the host server of the server system 112 in step 712. Any remnants of the apphcation program are then removed from the operating system 135 and local drives generally, in step 714. Specifically, any modified registry settings are returned, icons are removed, folders in any disk drive are removed, and any new copies of applications on desktop are removed.
  • this follow-up URL is for the subscribing institution and is typically hosted by the web server 130, allowing it to follow with a "sales pitch" or to solicit for further purchase of goods and/or services. This allows, in some implementations, the third-party application hosting to be transparent to the user at the target computer. Finally, any remaining momtoring processes are identified in step 720, and the monitoring processes are terminated in step 722.
  • step 724 the application is quit and the software player is shut down in step 726.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Communication Control (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé et un système conçus pour servir des applications logicielles à des clients à distance par le biais d'Internet. Par exemple, selon l'invention, on utilise, de préférence, des protocoles type SMB (server message block), disponibles dans des systèmes d'exploitation courants. En outre, l'invention traite d'un procédé commercial associé dans lequel les institutions abonnées peuvent externaliser, en toute transparence, l'application servant à une institution tierce.
PCT/US2000/009833 1999-04-12 2000-04-12 Procede et systeme de desserte d'application logicielles WO2000062161A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU42361/00A AU4236100A (en) 1999-04-12 2000-04-12 Method and system for serving software applications

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12882899P 1999-04-12 1999-04-12
US60/128,828 1999-04-12

Publications (2)

Publication Number Publication Date
WO2000062161A2 true WO2000062161A2 (fr) 2000-10-19
WO2000062161A3 WO2000062161A3 (fr) 2001-03-01

Family

ID=22437179

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/009833 WO2000062161A2 (fr) 1999-04-12 2000-04-12 Procede et systeme de desserte d'application logicielles

Country Status (2)

Country Link
AU (1) AU4236100A (fr)
WO (1) WO2000062161A2 (fr)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1217799A1 (fr) * 2000-12-22 2002-06-26 Sun Microsystems, Inc. Exécution côté serveur de modules d'application dans un système client-serveur
US6574618B2 (en) 1998-07-22 2003-06-03 Appstream, Inc. Method and system for executing network streamed application
WO2002077809A3 (fr) * 2001-03-27 2003-11-27 Isource Concepts Inc Creation et distribution d'instructions securisees destinees uniquement a des applications reseau
US6757894B2 (en) 2000-09-26 2004-06-29 Appstream, Inc. Preprocessed applications suitable for network streaming applications and method for producing same
WO2003093989A3 (fr) * 2002-04-30 2004-09-16 Accenture Global Services Gmbh Gestion de logiciel
US7197570B2 (en) 1998-07-22 2007-03-27 Appstream Inc. System and method to send predicted application streamlets to a client device
US7606924B2 (en) 1998-07-22 2009-10-20 Symantec Corporation Method and apparatus for determining the order of streaming modules
US7680758B2 (en) 2004-09-30 2010-03-16 Citrix Systems, Inc. Method and apparatus for isolating execution of software applications
US7752600B2 (en) 2004-09-30 2010-07-06 Citrix Systems, Inc. Method and apparatus for providing file-type associations to multiple applications
US7853947B2 (en) 2004-09-30 2010-12-14 Citrix Systems, Inc. System for virtualizing access to named system objects using rule action associated with request
US8117559B2 (en) 2004-09-30 2012-02-14 Citrix Systems, Inc. Method and apparatus for virtualizing window information
US8171479B2 (en) 2004-09-30 2012-05-01 Citrix Systems, Inc. Method and apparatus for providing an aggregate view of enumerated system resources from various isolation layers
US9009720B2 (en) 2007-10-20 2015-04-14 Citrix Systems, Inc. Method and system for communicating between isolation environments

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020087717A1 (en) 2000-09-26 2002-07-04 Itzik Artzi Network streaming of multi-application program code
US8095940B2 (en) 2005-09-19 2012-01-10 Citrix Systems, Inc. Method and system for locating and accessing resources
US8131825B2 (en) 2005-10-07 2012-03-06 Citrix Systems, Inc. Method and a system for responding locally to requests for file metadata associated with files stored remotely
US7779034B2 (en) 2005-10-07 2010-08-17 Citrix Systems, Inc. Method and system for accessing a remote file in a directory structure associated with an application program executing locally
US8090797B2 (en) 2009-05-02 2012-01-03 Citrix Systems, Inc. Methods and systems for launching applications into existing isolation environments

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5708709A (en) * 1995-12-08 1998-01-13 Sun Microsystems, Inc. System and method for managing try-and-buy usage of application programs
US6067582A (en) * 1996-08-13 2000-05-23 Angel Secure Networks, Inc. System for installing information related to a software application to a remote computer over a network

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6574618B2 (en) 1998-07-22 2003-06-03 Appstream, Inc. Method and system for executing network streamed application
US7197570B2 (en) 1998-07-22 2007-03-27 Appstream Inc. System and method to send predicted application streamlets to a client device
US7606924B2 (en) 1998-07-22 2009-10-20 Symantec Corporation Method and apparatus for determining the order of streaming modules
US6757894B2 (en) 2000-09-26 2004-06-29 Appstream, Inc. Preprocessed applications suitable for network streaming applications and method for producing same
EP1217799A1 (fr) * 2000-12-22 2002-06-26 Sun Microsystems, Inc. Exécution côté serveur de modules d'application dans un système client-serveur
US7257615B2 (en) 2000-12-22 2007-08-14 Sun Microsystems, Inc. Server side execution of application modules in a client and server system
WO2002077809A3 (fr) * 2001-03-27 2003-11-27 Isource Concepts Inc Creation et distribution d'instructions securisees destinees uniquement a des applications reseau
WO2003093989A3 (fr) * 2002-04-30 2004-09-16 Accenture Global Services Gmbh Gestion de logiciel
US7680758B2 (en) 2004-09-30 2010-03-16 Citrix Systems, Inc. Method and apparatus for isolating execution of software applications
US7752600B2 (en) 2004-09-30 2010-07-06 Citrix Systems, Inc. Method and apparatus for providing file-type associations to multiple applications
US7853947B2 (en) 2004-09-30 2010-12-14 Citrix Systems, Inc. System for virtualizing access to named system objects using rule action associated with request
US8042120B2 (en) 2004-09-30 2011-10-18 Citrix Systems, Inc. Method and apparatus for moving processes between isolation environments
US8117559B2 (en) 2004-09-30 2012-02-14 Citrix Systems, Inc. Method and apparatus for virtualizing window information
US8171479B2 (en) 2004-09-30 2012-05-01 Citrix Systems, Inc. Method and apparatus for providing an aggregate view of enumerated system resources from various isolation layers
US9009720B2 (en) 2007-10-20 2015-04-14 Citrix Systems, Inc. Method and system for communicating between isolation environments
US9009721B2 (en) 2007-10-20 2015-04-14 Citrix Systems, Inc. Method and system for communicating between isolation environments
US9021494B2 (en) 2007-10-20 2015-04-28 Citrix Systems, Inc. Method and system for communicating between isolation environments

Also Published As

Publication number Publication date
WO2000062161A3 (fr) 2001-03-01
AU4236100A (en) 2000-11-14

Similar Documents

Publication Publication Date Title
US8612514B2 (en) Serving software applications from servers to client computers
US7200632B1 (en) Method and system for serving software applications to client computers
US6938096B1 (en) Method and system for remote networking using port proxying by detecting if the designated port on a client computer is blocked, then encapsulating the communications in a different format and redirecting to an open port
WO2000062161A2 (fr) Procede et systeme de desserte d'application logicielles
US6915519B2 (en) Pluggable JMS providers in a J2EE server
US7389219B2 (en) Provisioning computing services via an on-line networked computing environment
CA2370997C (fr) Interrogation et certification visant les capacites d'un ordinateur eloigne
EP0981885B1 (fr) Dispositif et procede permettant d'identifier les clients qui accedent a des sites de reseau
US5974566A (en) Method and apparatus for providing persistent fault-tolerant proxy login to a web-based distributed file service
US9386083B2 (en) Managed services platform
US7650390B2 (en) System and method for playing rich internet applications in remote computing devices
US9338217B2 (en) Method and apparatus for computing within a wide area network
US8219849B2 (en) Method and apparatus for controlling a computer over a wide area network
US20030084439A1 (en) Incentive system for distributing software over a computer network
US20070294334A1 (en) Method and apparatus for controlling a computer over a TCP/IP protocol network
US7162744B2 (en) Connected support entitlement system and method of operation
US7730169B1 (en) Business method and system for serving third party software applications
US6430739B1 (en) Software execution contingent on home page setting
US20030023752A1 (en) Pluggable URL providers in a J2EE server
Revett et al. Network computing: a tutorial review
WO2003044662A1 (fr) Augmentation ou diminution incrementielle des fonctionnalites disponibles d'un programme d'ordinateur
WO2001055876A1 (fr) Dispositif web
JPH10334046A (ja) ホスト・コンピュータ・プログラムに対する対話式インターネット・アクセスのためのシステム、方法、及び装置
WO2001004752A2 (fr) Procede et systeme pour permettre a des utilisateurs eventuels de tester et d'utiliser un logiciel via un reseau informatique

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载