Advanced eGovernment Information Service Bus (eGov-Bus)

The eGov-Bus project provides citizens and businesses with improved access to virtual public services, which are based on existing national eGovernment Web services and which support cross-border life events. Requirements and specific rules of these life events are considered, and personalization of user preferences is supported. eGov-Bus is based on adaptable process management technologies, allowing for virtual services which are dynamically combined from existing national eGovernment services. In this way, a comprehensive workflow process is set up, allowing for service-level agreements, an audit trail and explanation of the process to the end user. The eGov-Bus process engine operates on top of a virtual repository, providing a high-level semantic view of information retrieved from heterogeneous information sources, such as eGovernment Web services. Further, eGov-Bus relies on a security framework to ensure all high-level security requirements are met. The eGov-Bus architecture is business oriented, it focuses on Service Oriented Architecture (SOA) concepts, asynchronously combining Web services and providing a Service Bus.Frameworks and Guidelines, eGovernment Ontologies, Admininistrative Process Design, Life Events, Web Services, Service Bus Integration

Developing a Web Server Platform with SAPI support for AJAX RPC using JSON

Writing a custom web server with SAPI support is a useful task which helps students and future system architects to understand the link between network programming, object oriented programming, enterprise application designing patterns and development best practices because it offers a vision upon interprocess communication and application extensibility in a distributed environmentWeb, Server, Proxy, SAPI, HTTP, RPC, AJAX, JSON, XML

Ajax Mistakes

Ajax, shorthand for Asynchronous JavaScript and XML, is a web development technique for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire web page does not have to be reloaded each time the user requests a change. This is meant to increase the web page's interactivity, speed, and usability. However, there are several common mistakes using it, like: using Axaj just for the sake of Ajax, moreover the back button of the browser become unuseful, there might be a delay displaying enhanced GUI widgets, offline content is not supported, concurrent page loading is dramatically slowed down, sensitive information might be sent encrypted, cross-browser implementation is not one of developers primary concerns, concurrent access is not well supported, running the entire application on the client side makes it slower, there is no support for user without a JavaScript enable browser, GUI might change unexpectedly, there are no URLs which may be referred and indexed by users and search engines, pop-up blockers might kill opening windows, there are a lot of asynchronous operations happening in the background which might be difficult to be controlled, inventing new controls which are less intuitive than the classic ones, style and internationalization issues due to partial page rendering, the lack of data posted back from the user, Web traffic cannot be reported for each section of a given site.Web Technologies, Web Frameworks, AJAX, Asynchronous HTTP Request, User-friendly Interfaces