Clojure
Rich Hickey discusses Clojure features and syntax, example code, functional programming, concurrency semantics, transactions, software transactional memory, agents, implementation and pain points.
- Java,
Tracking change and innovation in the enterprise software development community
Posted by Mark Little on Jan 11, 2007 10:27 AM
For years people have debated that "SOAP is too slow" and Web Services are just marketing hype. Although it is fair to say that SOAP is slow, it's getting better and one of the more interesting advances came with the development of the SOAP Message Transmission Optimization Mechanism (MTOM) specification. MTOM has quickly become an important component within the Web Services developers arsenal, offering the composability of base64 with the transport efficiency of SOAP with attachments. But unfortunately it wasn't tied into the rest of the Web Services architecture: there was no standard way for services to advertise that they were "MTOM ready". Until today that is.
IBM and Microsoft have recently submitted WS-MTOMPolicy to W3C. This has now been acknowledged by W3C, which opens the way for a standardization effort around this. As the abstract says:
This specification describes a domain-specific policy assertion that indicates endpoint support of the optimized MIME multipart/ related serialization of SOAP messages defined in section 3 of the SOAP Message Transmission Optimization Mechanism specification. This policy assertion can be specified within a policy alternative as defined in WS-Policy Framework and attached to a WSDL description as defined in WS-PolicyAttachment.
With this combination of WS-Policy and MTOM, it's soon going to be possible for Web Services across enterprise boundaries to advertise their MTOM capabilities. This could be one of the first practical uses of WS-Policy.
Agile Projects: Five Ways to Fail When You Scale
Smart agile development within dispersed teams
How to use Open Source SOA Safely in the Enterprise
The Key to SOA Governance: Understanding the Essence of Business
Webcast: Applying lean thinking to the governance of software development
Rich Hickey discusses Clojure features and syntax, example code, functional programming, concurrency semantics, transactions, software transactional memory, agents, implementation and pain points.
We introduce the concept of Composite Oriented Programming, and show how it avoids the issues with OOP and reignites the hope of being able to compose domain models with reusable pieces.
Dan Farino talks about the system architecture and the challenges faced when building a very large online community. Dan explains how a .NET product scales on hundreds of servers.
Alan Shalloway, CEO and founder of Net Objectives, presents the Lean software development principles and practices and how they can benefit to Agile practitioners.
Bernd Mathiske discusses Maxine VM, Java compatibility, swapping major VM components, research areas, Object handling, code examples, optimizing compiler, snippets, bytecode generation, JNI and JIT.
Joe Armstrong speaks on various aspects of the Erlang language, presenting its roots, how it compares with other languages and why it has become popular these days.
The java double-check singleton pattern is not thread safe and can’t be fixed. In this article, Dr. Alexey Yakubovich provides an implementation of the Singleton pattern that he claims is thread-safe.
Diana and Jim talk about patterns observed in CTOs' activity. CTOs emerge as real people caring for other people in their organization, and are put under a lot of pressure and constraints.
No comments
Reply