Design & Architecture

The principles of WOA are:

1. It is a resource-oriented architecture (ROA) - so it is based on URIs and hyper-links

2. It is based on the web protocols for discovery and consumption - e.g. granular stateless services using REST much like with SOA.

3. It encourages linked-data - so different apps and data can reuse APIs and vocabularies to support mashups (WEB3.0).

4. Open yet secured

 

 

http://hinchcliffe.org/archive/2009/12/14/18179.aspx

 

udid 31/12/2009 - 10:21

 Agenda

  1. MVVM pattern
  2. WPF basics
  3. Demo
  4. Q&A

 

michael 03/10/2010 - 20:18

MVC based applications often offer some kind of a mediation between the actual Flex view component and the rest of the system.

PureMVC has its Mediator, Cairngorm offer the View Helper (though they not encourage using it). I'll focus on PureMVC.

 

When the view component is dynamically created, you'll probably want to create it's mediator dynamically as well.  This is a very common scenario in large applications.

 

First thing comes to mind in this scenario is using the view component's CreationComplete or Initialize events for creating its mediator.
 

It is very tempting doing so, especially when guaranteed that by the time these events occur, the component children are created, and the mediator can access them without getting exceptions.

 

The problem

ilan 04/08/2010 - 22:36

I was thinking over the past couple of weeks about my own personal take on open source development and where I fit in it:

We've all been there once or twice before - or, at least, saw it so happen to the guy behind the next flat screen - taking part in a dead-end project, no hope for reaching maturity; delirious mind start-ups that somehow sprung into existence, waiting from the first moment to be redeemed by the sound of closing taps, in the meantime taking up your day, your energies; situations where inner politics thrive and professionalism isn't sought after; you find yourself thinking about avoiding bug fixes, avoiding the next wave of dismissals, avoiding innovativeness - what for, right?

 

zvika 07/08/2009 - 03:13

respectively of the amount of accomplished projects, a new problem is not an easy task to solve even if there is some basic information about the requirements or technology to be used. An already existing development environment and culture could greatly improve and advance the software development process, but the issue of taking new technologies and tools into use cannot be ignored or bypassed. Today, Java-world is highly diversified, and could cover most of the tasks to be achieved.

lior.kanfi 11/02/2009 - 16:37
Syndicate content