SOA
[1/6] from: jblake::arsenaldigital::com at: 1-Jun-2006 9:13
Guys,
How stable do yall think the SOA stuff is?
I am thinking of building a little app to display counts of specific
records from a dbase. I'm under the impression that if my higher ups see
it, they are going to want it on their laptops. I thought about a direct
connection to the server from each client to get the data and that would
work. It's just if I need to change something, I'll have to deal with
updating all the apps on the laptops and I don't think I want to mess
with that.
So, I'm thinking the SOA.
Thoughts?
John
[2/6] from: ale870:gma:il at: 1-Jun-2006 15:27
Hello John,
SOA is more a concept than a program. Basically SOA suggests to use
Web Services to interface rich clients and servers.
If you don't need to use web services, I suggest you to create in the
server some web pages, but not returning HTML but returning Rebol
structures.
In this way, you can use simple GET/POST message to send data to the
server, and you can retrieve the results very fast.
--Alessandro
On 6/1/06, John Blake <jblake-arsenaldigital.com> wrote:
[3/6] from: carl:cybercraft at: 2-Jun-2006 2:09
On Thursday, 1-June-2006 at 15:27:27 Alessandro Manotti wrote,
>Hello John,
>SOA is more a concept than a program. Basically SOA suggests to use
<<quoted lines omitted: 4>>
>In this way, you can use simple GET/POST message to send data to the
>server, and you can retrieve the results very fast.
And update the client apps that way too.
-- Carl Read.
[4/6] from: ale870::gmail at: 1-Jun-2006 16:47
You could use JellAP, which contains a system to automatically update
clients without the need to implement any code in your application
:-)
--Alessandro
On 6/1/06, Carl Read <carl-cybercraft.co.nz> wrote:
[5/6] from: greggirwin:mindspring at: 1-Jun-2006 9:30
Hi John,
JB> How stable do yall think the SOA stuff is?
As someone said, SOA is a concept, or a model, so "stability" doesn't
really apply. Is it a sound architectural model? You bet. Of course,
there's a huge gray area about what qualifies as SOA too. :\
REBOL was designed for messaging. You could easily write a little app
that requests data via CGI, a direct server connection, RebServices,
etc. and displays that. Piece of cake.
Now, with REBOL, you can just as easily request a small script, so
you're dynamically requesting the app to run, GUI and all. You could
also use the browser plug-in to avoid deployment issues.
-- Gregg
[6/6] from: jblake::arsenaldigital::com at: 1-Jun-2006 13:15
Thanks for all the info guys.
I'm thinking of having 2 scripts on the server side;
1 to get the dbase info to put it in a file (say every 20 minutes).
The 2nd to read the file every 10 minutes and to respond to client
requests for that info.
That way, the clients won't cause lots of sql queries to the dbase when
the client updates the view.
Humm...
Maybe this could be an option for one of the configurable little apps
they are looking for to show what REBOL can do.
Have 1 script do the sql to get any results needed and output to file.
Have "server" script read file and have info available for clients.
Have client GUI's designed to display different sql results (depending
on what you configure on the server).
What do you guys think?
I'm probably thinking of this wrong as I'm defiantly a newbe.
John
Notes
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted