Split client-server software development architecture

• US 20020174193A1
• Filed: 04/30/2001
• Published: 11/21/2002
• Est. Priority Date: 04/30/2001
• Status: Abandoned Application

• Current Assignee: Ixcelerator Com Limited
• Original Assignee: Ixcelerator Com Limited
• Inventors: Mikhalchuk, Andrei Sergeevich
• Application Number:
  US09/843,935
• Publication Number:
  US 20020174193A1
• Time in Patent Office: Days
• US Class Current: 709/219
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A split client-server software development architecture including a client, at least one software module resident on the client, a network, a server, and a core application resident on the server, where the client is operative to upload the at least one software module to the server via the network, and the server is operative to couple the core application and the at least one software module and instate an application instance formed therefrom.

Claims

1. A split client-server software development architecture comprising:

a client;

at least one software module resident on said client;

a network;

a server; and

a core application resident on said server,

wherein said client is operative to upload said at least one software module to said server via said network, and

wherein said server is operative to couple said core application and said at least one software module and instantiate an application instance formed therefrom.

2. An architecture according to claim 1 wherein said software module is in either of a source code and an object code format.

3. An architecture according to claim 1 wherein said software module includes at least one application programming interface (API) call to a procedure included in said core application.

4. An architecture according to claim 1 wherein said core application includes at least one application program interface (API) call to a procedure included in said software module.

5. An architecture according to claim 1 wherein said client is operative to upload said at least one software module to said server via said network using the File Transfer Protocol (FTP).

6. An architecture according to claim 1 wherein said client is operative to upload at least one configuration parameter to said server identifying said core application.

7. An architecture according to claim 1 wherein said client is operative to upload at least one configuration parameter to said server identifying at least one supporting module resident on said server and wherein said server is operative to couple said core application said at least one software module, and said at least one supporting module and instantiate an application instance formed therefrom.

8. An architecture according to claim 1 wherein said client is operative to provide input to said application instance via said network.

9. An architecture according to claim 1 wherein said application instance is operative to provide output to said client via said network.

10. An architecture according to claim 1 wherein said client comprises development apparatus for interfacing with a user and receiving said at least one software module therefrom.

11. An architecture according to claim 10 wherein said development apparatus is operative to upload said at least one software module to said server.

12. An architecture according to claim 10 wherein said development apparatus is operative to upload at least one configuration parameter to said server.

13. An architecture according to claim 1 wherein said server is operative to couple said at least one software module with a previously instantiated application instance.

16. A method according to claim 15 wherein:

said developing step comprises developing said at least one plug-in module to interface with at least one supporting module on said server,

said communicating step comprises communicating to said server an identifier identifying said at least one supporting module to be used with said plug-in module, and

said creating comprises creating an application instance on said server comprising said core application, said plug-in module, and said supporting module.

17. A method according to claim 15 wherein said creating step comprises creating a plurality of instances of said application on said server.

14. A split client-server software development architecture comprising:

a client;

a network;

a server;

a core application resident on said server; and

at least one software module resident on said server,

wherein said server is operative to couple said core application and said at least one software module and instantiate an application instance formed therefrom, and

wherein said client is operative to control said application instance by sending at least one command to said server via said network.

15. A split client-server software development method comprising the steps of:

developing at least one plug-in module at a client for interfacing with a core application on a server;

uploading said plug-in module to said server;

communicating to said server an identifier identifying said core application to be used with said plug-in module;

creating an application instance on said server comprising said core application and said plug-in module; and

executing stud application on said server.