Page 1 of 1

interaction between client and server

Posted: Tue Jul 26, 2005 9:49 am
by djot
-
Regarding interaction between client and server ...

Is there something coming up in near feature, that enables browser to not only act as client, fetching only complete websites?

Please exclude java, flash, ie-only push technology, third-party products/plugins and suchalike from your answers.


djot
-

Posted: Tue Jul 26, 2005 10:06 am
by pickle
You want something that'll download complete websites, but you don't want third-party products or plugins? Kind of limiting the field a bit eh?

Posted: Tue Jul 26, 2005 10:13 am
by djot
-
No, I don't want to download complete websites. But I don't like to use Java or whatever to have some interaction. I think this is dramatically missing in the inet. What is the next coming up killing app that will allow some interaction? Using only HTML and sorry, this <span style='color:blue' title='I&#39;m naughty, are you naughty?'>smurf</span> javascript/java, can't be the solution for the next few years.

djot
-

Posted: Tue Jul 26, 2005 10:28 am
by timvw
Meaby you can try to explain what you mean with interaction...


If you start coupling the server and client more.. you will end up with a fat-client.. And we've been there already..

Posted: Tue Jul 26, 2005 10:36 am
by djot
-
Yes, you're right. But mixing up 5 or more technologies for just one website is also not a clean solution.

I am currently working in a company with 80% of freelancers. Each one codes what he is best in or prefers most. Each single coding has its advantages and disadvantages. Integrating all this is really horrible. Also everyone has to be an expert in his area, and its impossible to even have an overview over all sections.

djot
-

Posted: Tue Jul 26, 2005 10:54 am
by timvw
Imho, it's a level of abstraction.

I care about the interface i have with the system (usually the html pages) and don't give a smurf about how this is done ;)

I've already said that i like XML/XSL. Because all we had to do is specify how the XML will look like (eventually compile a DTD/XSD). And from there it is up to the designers to generate a sexy (X)HTML/Flash/Whatever layout using XSL... And all we programmers have to do is make sure we come up with the required XML...

So the designers only have to learn XSL.. And they don't give a smurf about the other applied technologies(php, jsp, ..)

Offcourse it was/is/and will always be a matter of selecting the right tools for the job...

Posted: Tue Jul 26, 2005 11:12 am
by nielsene
djot wrote:-
Yes, you're right. But mixing up 5 or more technologies for just one website is also not a clean solution.

I am currently working in a company with 80% of freelancers. Each one codes what he is best in or prefers most. Each single coding has its advantages and disadvantages. Integrating all this is really horrible. Also everyone has to be an expert in his area, and its impossible to even have an overview over all sections.

djot
-
To some degree all large scale computer applications span multiple technologies. Take a large Java project, say one for a word processor. It will have lots of Java, of course, an obscene amount of XML configuration/build scripts. Many of the populate layout managers for the dialog boxes/screen/interfaces are effectively another languange, etc. There's always a mix; you want to use the right tool for the right job and this will almost always mean mixing some tools.