Introducing the FireCracker!
Based on Analog Devices popular Blackfin embedded processor, Silica has developed the FireCracker Development and Reference Design Platform for audio and video applications. FireCracker is a unique concept of a hybrid between a development board and a reference design that enables design engineers to bring embedded computing solutions from concept to production in record time.

Got Talent? Need Talent? Find or list design services now!

paper    

An XML Web Services Development Environment for Embedded Devices
The ubiquitous nature of XML makes it a undeniably compelling data interchange format promising universal access to any XML-enabled device by any XML-enabled application. Industry-standard XML-based Web services protocols provide new opportunities to achieve enterprise systems integration, but their use in embedded systems is a challenge.
preview: http://websrv.cs.fsu.edu  

paper    

Integration of Embedded Devices Through Web Services: Requirements, Challenges and Early Results
Integration of the currently available computing systems and platforms is one of the most envisaged goals achie-ved by computer scientists, which starts to become a re-ality nowadays. System integration technologies, such as Web Services, can provide a middleware for systems that were originally independent. This technology is being em-ployed successfully for the integration of business software, allowing the interaction between...
preview: http://www.inf.ufsc.br  

paper    

SOAP Web Services Attacks
This white paper discusses various types of attacks based on the SOAP implementation of Web services over HTTP and describes how you can shield your applications from these assaults. Other types of attacks are possible and detailed descriptions of those will be available in upcoming white papers. This paper is not intended to fully describe SOAP, but rather to present a brief overview of key web services concepts.
preview: http://www.spidynamics.com  

paper    

The Web Services Kernel
Don Box presented a set of (mildly hallucinogenic [1]) slides at the XML Developers Conference on the topic of WS-Why? The goal of the talk was to provide some background on the various WS-* specifications and contextualize them a bit to talk more about the intent of the specs as opposed to their mechanics. This essay is a remixed version of the first part of Don’s talk, interspersed with some of my own noodlings.
preview: http://hyperthink.net  

overview    

A Web Services Primer
From a service API point of view, the majority of the web's work is done by 3 methods (GET, POST, and PUT) and a simple markup language. The web services movement is about the fact that the advantages of the Web as a platform apply not only to information but to services.
preview: http://webservices.xml.com  

overview    

SOAP - Simple Object Access Protocol
SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses.
preview: http://www.w3.org  

overview    

Top Ten FAQs for Web Services
Web services represent an important evolutionary step in building distributed applications. But, what exactly is a Web service? What is the Web service protocol stack? And, does the World Wide Web Consortium support any Web service standards?
preview: http://www.oreillynet.com