Architecture: what do you use to make websites build with Umbraco a RIA solution.
Hello all,
I have a
question about architecture. As a test for myself I’m building a website with
Umbraco. I see you can do quite a lot with Umbraco. But as usual I want more J For example: I’m now making a news
ticker element like you can see on the BBC news site. Not spectacular
functionality, but it’s to try things in Umbraco.
Before I go
on I like to add that I really believe in SOA type of solutions. This means
that I will use as much as possible Web services.
I realize I can create the data for a JavaScript
in the dynamic html page. But I prefer to make a RIA component that connects to
a web service, and the web service gives the data to be displayed in the news
ticker.
Now this
RIA component can made with several techniques. The options I’m thinking about
right now are:
-JavaScript
based on DOJO + WCF backend
-JavaScript
based on jQuery + WCF backend
-Microsoft
Ajax control + WCF
-Telerik
+ WCF (read commercial product including
support as base)
-Adobe
Flex + either direct WCF as backend
-Adobe
Flex with FluorineFX as communication layer to WCF backend
-Silverlight
+ WCF backend
-Some
other solution
Now what i
like to ask is this: what do you use, what options did you consider and are you
happy with your choice.
I know it
seems a very open question. But see this question as an architecture question. The simple variant of this question is: What do you use to make websites build
with Umbraco a RIA solution.
For something that's going to be a "one off", building a dedicated DocumentType and Template that outputs your XML or JavaScript is probably the easiest.
For a set of services that return a small amount of data, umbraco base would probably be a better choice.
For an application that has heavy amounts of data going back and forth, FluorineFx would be the best choice. There is also a free community edition of WebOrb for .NET. I think WebOrb is easier to deal with, but it's not open source and the licensing model for the free edition will only allow you one site/license.
I would probably also go with BASE for that kind of communication with umbraco.
A side note here is that WCF services do not play well with umbraco in my experience, because the WCF configuration conflicts with some umbraco functionality, so you would need something like a separate host name (services.example.com) for the site in order to host WCF services in the umbraco website. I have not done this myself, but can dig up some info if you prefer WCF to the base/REST type communication.
Architecture: what do you use to make websites build with Umbraco a RIA solution.
Hello all,
I have a question about architecture. As a test for myself I’m building a website with Umbraco. I see you can do quite a lot with Umbraco. But as usual I want more J For example: I’m now making a news ticker element like you can see on the BBC news site. Not spectacular functionality, but it’s to try things in Umbraco.
Before I go on I like to add that I really believe in SOA type of solutions. This means that I will use as much as possible Web services.
I realize I can create the data for a JavaScript in the dynamic html page. But I prefer to make a RIA component that connects to a web service, and the web service gives the data to be displayed in the news ticker.
Now this RIA component can made with several techniques. The options I’m thinking about right now are:
Now what i like to ask is this: what do you use, what options did you consider and are you happy with your choice.
I know it seems a very open question. But see this question as an architecture question.
The simple variant of this question is: What do you use to make websites build with Umbraco a RIA solution.
Frank Gillebaard.
Going to throw umbraco base out there as another option for you:
http://umbraco.org/documentation/books/introduction-to-base
For something that's going to be a "one off", building a dedicated DocumentType and Template that outputs your XML or JavaScript is probably the easiest.
For a set of services that return a small amount of data, umbraco base would probably be a better choice.
For an application that has heavy amounts of data going back and forth, FluorineFx would be the best choice. There is also a free community edition of WebOrb for .NET. I think WebOrb is easier to deal with, but it's not open source and the licensing model for the free edition will only allow you one site/license.
I would probably also go with BASE for that kind of communication with umbraco.
A side note here is that WCF services do not play well with umbraco in my experience, because the WCF configuration conflicts with some umbraco functionality, so you would need something like a separate host name (services.example.com) for the site in order to host WCF services in the umbraco website. I have not done this myself, but can dig up some info if you prefer WCF to the base/REST type communication.
is working on a reply...