1. How does IBM® Sharable Code compare to other IBM Mashup projects?
IBM Sharable Code is a different project than the currently available IBM Mashup Starter Kit (also here on alphaWorks®). In particular, IBM Sharable Code is completely implemented in Ruby on Rails. IBM Sharable Code also takes a domain-specific language (DSL) approach to represent mashups. We are working to interoperate with and be integrated with the other IBM mashups projects, and we might release a new, integrated version in the future.
2. Why use a domain-specific language (DSL)?
The main differences are as follows:
A DSL allows for a high-level representation of a domain. The domain in question for us is the Web, Web APIs, Web applications, and so on. Using the DSL, we abstract the details of the different API into a uniform language and allow the various constructs of the language to be shared and combined. We intend to continue improving the DSL as well as the tools to make creating the various DSL constructs easier.
3. Can the DSL be represented in XML?
Yes. We will have a version for this in the next release.
4. Why use Ruby and Rails (RoR) as the underlying implementation?
By using RoR, we inherit a rich platform for agile Web 2.0 application development and a great language for DSL development.
5. Why can't the builder allow deployments of mashups and testing (in an agile fashion)?
We had to disable this feature from the current release because it required the opening of new ports from the alphaWorks servers, and this can have security consequences. We are working on an alternate design and implementation that will make deployment of mashups into our servers, a cloud of servers, or your servers feasible directly from within the platform. Please join the forum discussion to give us your opinion.
6. Can the IBM Sharable Code mashups deployments be automated?
Yes. This feature was disabled. See the previous question.
IBM and alphaWorks are trademarks of IBM Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
|
Date Posted: December 11, 2007
|
