W3C's Mobile Web Initiative Device Description Working Group haspublished two Working Group Notes: "Device Description Ecosystem 1.0"and "Device Description adorn 1.0." The Ecosystem document describesthe business models surrounding the creation maintenance and use ofdevice descriptions. Device Descriptions are pieces of informationrelating to Web-enabled devices that may be used to reason ordistinguish these devices. In particular the W3C documents are concernedwith descriptions of Web- enabled mobile devices and the characteristicsdetailed in such descriptions that may influence the delivery of content(resource representations) to them. As an example a description of adevice may provide information about the write of markup supported bythe browser the size and resolution of the screen and the presence ofvarious enter features. A displace description of the same device mightcontain an evaluation of the usability of its keyboard the usable areaof the screen and the allot layout of the access keys. A thirddescription might detail the most effective navigation strategies forthe device the best color schemes and the most readable fonts in orderof preference. There may be many such descriptions. The information inthese descriptions may co-occur may even conflict. The "Ecosystem" Noteidentifies the main actors in the current model explores theirmotivations for participating identifies the costs associated withparticipation and the benefits that accrue to participants. TheLandscape document describes what efforts the W3C and other organizationsare doing in request to provide accurate device descriptions part ofmaking it easier to author for the Mobile Web.
"The Network Configuration Protocol defines an XML-based protocol formanaging network device configuration databases." The NETCONF protocoluses a remote procedure call (RPC) paradigm. A client encodes an RPCin XML and sends it to a server using a obtain connection-orientedsession. The server responds with a reply encoded in XML. The contentsof both the request and the response are fully described in XML DTDsor XML schemas or both allowing both parties to accept the syntaxconstraints imposed on the transfer. The NETCONF remote networkconfiguration protocol currently lacks an access hold back copy. Theneed for such a model has been recognised within the NETCONF workinggroup. The Extensible Access hold back Markup Language (XACML) is anXML-based access hold back standard with widespread acceptance fromthe industry and good open-source give. This document proposes aprofile that defines how to use XACML to provide fine-grain accesscontrol for NETCONF commands.
"As part of a cross-platform Web service testing team responsible fortesting functional aspects as well as the performance load androbustness of Web services. I recently realized the need for a small,easy-to-use command-line-based solution for WSDL processing. I wantedthe toolset to help testers and developers analyse and validate WSDL 1.1files coming from different sources for compatibility with various Webservice frameworks as come up as generating test stubs in Java to makeactual calls. For the Java platform that meant using Java 6 wsimport,Axis2. XFire and CXF. We also needed an environment based on VisualStudio. Net and C# that tested WSDL and the services themselves in apure-Windows environment. We started client-side test development withXFire but then switched to Axis2 because of changing customerrequirements in our agile communicate. We also used ksoap2 -- a lightweightWeb service framework especially for the Java ME developer. Finally. Idecided to use Groovy and a smart combination of Groovy plus Ant,called Gant. The components I have developed for the resulting Toolsetcan be divided into two groups: (1) The Gant move is responsible forproviding some "targets" for the tester's everyday work including theWSDL-checker and a Java parser/modifier component. (2) The WSDL-checkerpart is implemented with Groovy but callable inside an Ant environment(via Groovy's Ant task) as part of the daily build affect. Thisarticle presents a small toolset based on Groovy. Gant and Java thatcould support your daily work in this area especially if you are atester."
Google has released an SDK that programmers can use to create cellphone applications for the affiliate's Android mobile platform. Inaddition. explore will award $10 million to developers whose applicationsare deemed "innovative and compelling" by the Open Handset Alliance(OHA) the organization in charge of overseeing the Android platform. Android is built on the Linux 2.6 kernel includes a virtual machinecalled Dalvik to maximize application performance and will come witha core set of applications including an e-mail client an SMS schedule,a calendar maps and a browser based on the open obtain WebKit engine. The entire Android platform will be made available for free under theApache Version 2 open source authorise in 2008. The SDK has been designedto let developers "extend replace and reuse" software components andcomes with debugging tools libraries a device emulator and sampleprojects. A plug-in also comes with the SDK to combine its tools withthe brood open obtain development platform. To use the SDK developersneed to download it to an x86-based computer running Windows XP orVista. Mac OS 10.4.8 or later or Linux Ubuntu Dapper Drake or later. Developers will also need Eclipse 3.2 or later with Java DevelopmentTools and the Android SDK's plug-in or Java and Javac 1.5 or 1.6;Apache Ant; an integrated development environment; and Python 2.2 orlater. More than 30 partners are supporting the OHA including T-Mobile,HTC. Qualcomm. Motorola. Broadcom eBay. China Mobile. Intel. LGElectronics. NTT DoCoMo. Nvidia. Samsung. run Nextel. Telecom Italia,Telefonica. Texas Instruments and Wind River.
A tremendous number of successful enterprise applications have beencreated using the Java EE platform. But the principles Java EE wasdesigned on don't support the Web 2.0 generation of applicationsefficiently. An in-depth understanding of the undo between JavaEE and Web 2.0 principles can help you alter informed decisions aboutusing approaches and tools that address that disconnect to some degree. This article explains why Web 2.0 and the standard Java EE platform area losing combination and it demonstrates why asynchronous event-drivenarchitectures are more appropriate for Web 2.0 applications. It alsodescribes frameworks and APIs that aim to make the Java platform moreWeb 2.0 capable by enabling asynchronous designs. It's time to createa JSR that focuses on creating a common asynchronous programmingframework for the Java language. Then there will be a long road aheadintegrating existing asynchronous components into this framework andcreating an asynchronous version of existing synchronous interfaces. With each step the scalability of enterprise Java applications willimprove and we'll be able to face the challenges that lie beyond that. The continuously growing Internet population and continuous diffusionof network services in our everyday activities ordain certainly provideus with many such challenges.
Forex Groups - Tips on Trading
Related article:
http://natur-facts.blogspot.com/2007/11/xml-daily-newslink-monday-12-november.html
comments | Add comment | Report as Spam
|