sorted by: recent | see : popular

Content Tagged with remoting + Library

Clustered Remoting for Spring Framework (Cluster4Spring) represents an alternative implementation of the remoting subsystem of Spring framework and provides possibilities to build more stable and fault tolerant systems with dynamic discovering of remote services. Cluster4Spring uses Apache 2.0 license that allows using it both in commercial and non-commercial products.

Briefly, the major features of Cluster4Spring library are:

• Support of one-to-one scheme of remoting (similar to one currently supported by Spring);

• Support of one-to-many scheme of remoting, which assumes that one client selects remote service for invocation from one of predefined locations;

• Support of one-to-many scheme of remoting with dynamic discovering of remote services;

• Several built-in policies for selecting remote service for invocation are included (they are applied if service is available in several locations);
• Built-in functionality for handling remoting exceptions of method invocations that provides ability to re-invoke remote service using different service location automatically;
• Steep learning curve since ideological implementation of Cluster4Spring bears a close resemblance to the implementation of remoting in Spring;
• Non-intrusive for existing applications – it is simply enough to change appropriate remoting-related Spring configuration files to start using Cluster4Spring;
• Provides a convenient way to add custom interceptors both on client and server side;
• Flexible and modular architecture which is ready for further extensions and customizations;
• Library is stable and ready to use;

Another feature, which is currently missing in remoting subsystem offered by Spring framework, is lack of the ability to dynamically discover remote services.

The main purpose of Cluster4Spring is to extend remoting system of Spring framework and overcome limitations mentioned above.

The Cluster4Spring library was developed in SoftAMIS, a Ukraine based software development company specialized on Java and Web development outsourcing services. To find more about SoftAMIS, our services, skills and experience, please visit our site –

http://www.soft-amis.com

The home page of Cluster4Spring is located here

As3 RPC lib is a set of libraries that can be used with Flex 2 or AS 3 to invoke remote procedure calls using: * AMF0 (Flash Remoting MX) * XML-RPC * JSON-RPC (Coming Soon) Usage mimics the RemoteObject which is available natively in Flex 2

Clustered Remoting for Spring Framework (Cluster4Spring) represents an alternative implementation of the remoting subsystem of Spring framework and provides possibilities to build more stable and fault tolerant systems with dynamic discovering of remote services. Cluster4Spring uses Apache 2.0 license that allows using it both in commercial and non-commercial products.

Briefly, the major features of Cluster4Spring library are:

• Support of one-to-one scheme of remoting (similar to one currently supported by Spring);

• Support of one-to-many scheme of remoting, which assumes that one client selects remote service for invocation from one of predefined locations;

• Support of one-to-many scheme of remoting with dynamic discovering of remote services;

• Several built-in policies for selecting remote service for invocation are included (they are applied if service is available in several locations);
• Built-in functionality for handling remoting exceptions of method invocations that provides ability to re-invoke remote service using different service location automatically;
• Steep learning curve since ideological implementation of Cluster4Spring bears a close resemblance to the implementation of remoting in Spring;
• Non-intrusive for existing applications – it is simply enough to change appropriate remoting-related Spring configuration files to start using Cluster4Spring;
• Provides a convenient way to add custom interceptors both on client and server side;
• Flexible and modular architecture which is ready for further extensions and customizations;
• Library is stable and ready to use;

Another feature, which is currently missing in remoting subsystem offered by Spring framework, is lack of the ability to dynamically discover remote services.

The main purpose of Cluster4Spring is to extend remoting system of Spring framework and overcome limitations mentioned above.

The Cluster4Spring library was developed in SoftAMIS, a Ukraine based software development company specialized on Java and Web development outsourcing services. To find more about SoftAMIS, our services, skills and experience, please visit our site –

http://www.soft-amis.com

The home page of Cluster4Spring is located here

Clustered Remoting for Spring frawework

Clustered Remoting for Spring Framework (Cluster4Spring) represents an alternative implementation of the remoting subsystem of Spring framework and provides possibilities to build more stable and fault tolerant systems with dynamic discovering of remote services. Cluster4Spring uses Apache 2.0 license that allows using it both in commercial and non-commercial products.

Briefly, the major features of Cluster4Spring library are:

• Support of one-to-one scheme of remoting (similar to one currently supported by Spring);

• Support of one-to-many scheme of remoting, which assumes that one client selects remote service for invocation from one of predefined locations;

• Support of one-to-many scheme of remoting with dynamic discovering of remote services;

• Several built-in policies for selecting remote service for invocation are included (they are applied if service is available in several locations);
• Built-in functionality for handling remoting exceptions of method invocations that provides ability to re-invoke remote service using different service location automatically;
• Steep learning curve since ideological implementation of Cluster4Spring bears a close resemblance to the implementation of remoting in Spring;
• Non-intrusive for existing applications – it is simply enough to change appropriate remoting-related Spring configuration files to start using Cluster4Spring;
• Provides a convenient way to add custom interceptors both on client and server side;
• Flexible and modular architecture which is ready for further extensions and customizations;
• Library is stable and ready to use;

Another feature, which is currently missing in remoting subsystem offered by Spring framework, is lack of the ability to dynamically discover remote services.

The main purpose of Cluster4Spring is to extend remoting system of Spring framework and overcome limitations mentioned above.

The Cluster4Spring library was developed in SoftAMIS, a Ukraine based software development company specialized on Java and Web development outsourcing services. To find more about SoftAMIS, our services, skills and experience, please visit our site –

http://www.soft-amis.com

The home page of Cluster4Spring is located here

The “Clustered Remoting For Spring Framework” (or Cluster4Spring) is an alternative implementation of remoting subsystem included into Spring framework.

While implementation of remoting in Spring is great, it has several limitations that are quite important and must be taken into consideration when building large enterprise-level distributed system.

Briefly, these limitations relate to the point-to-point model of remoting supported by Spring – generally speaking, the client may use only one instance of remote service. It is obvious that having only such a scheme of remoting, it is hard to develop fault-tolerant systems and implement some kinds of load balancing.

Another feature, which is currently missing in remoting subsystem offered by Spring framework, is lack of the ability to dynamically discover remote services.

The main purpose of Cluster4Spring is to extend remoting system of Spring framework and overcome limitations mentioned above.

The Cluster4Spring library was developed in SoftAMIS, a Ukraine based software development company specialized on Java and Web development outsourcing services. To find more about SoftAMIS, our services, skills and experience, please visit our site –

http://www.soft-amis.com

The home page of Cluster4Spring is located here

UED is a tiny library that takes a hash and converts it into a URL. Instead of passing a JSON string, for example, you could just construct a URL containing the transfer object. Update: I should mention that this is more about the format than the library...UED is a proposal for a standard way to encode an object into a URL, in the same way that JSON is more a format than a library.

Since it assumes you are making GET calls, RESTful design would suggest only using UED for non-destructive calls (i.e. calls that don't change server state).

A hash is encoded like this:

leading to a URL like this:

However, there are no server-side decoders as yet.