 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Joao Morais
Guest
|
 Posted: Sat Apr 29, 2006 3:03 pm Post subject: Taligent's thin client |
 |
|
Hello,
In accordance with Taligent's paper, the presenter logic location
(application server or client) will decide if the application has a fat
or a thin client.
My implementation will share the model (only the model atm) between
application server and the client, so my application should be
considered an ultra-fat client :-)
Share the presenter between client and server is 'implementable',
although I don't know yet exactly how could I send model's events to the
view via wire. Perhaps listening 'pending process' whenever the client
presenter need to connect to the server presenter, maybe works.
So the question, how are you implementing thin client for desktop
applications? What are you placing into the client and what into the
application server? What about model's events? Or am I misunderstanding
everything?
--
Joao Morais |
|
| Back to top |
|
 |
Joanna Carter [TeamB]
Guest
|
| Posted: Sun Apr 30, 2006 1:03 pm Post subject: Re: Taligent's thin client |
|
|
"Joao Morais" <morais (AT) laserpress (DOT) srv.br> a écrit dans le message de news:
44537556$1 (AT) newsgroups (DOT) borland.com...
| So the question, how are you implementing thin client for desktop
| applications? What are you placing into the client and what into the
| application server? What about model's events? Or am I misunderstanding
| everything?
I would use remotable Presenter objects in .NET to allow the UI to consist
of the Presenter containing a real form View but linking that to remotable
Model and possibly Interactors.
Joanna
--
Joanna Carter [TeamB]
Consultant Software Engineer |
|
| Back to top |
|
|
Joao Morais
Guest
|
| Posted: Mon May 01, 2006 5:04 pm Post subject: Re: Taligent's thin client |
|
|
Joanna Carter [TeamB] wrote:
| Quote: | | So the question, how are you implementing thin client for desktop
| applications? What are you placing into the client and what into the
| application server? What about model's events? Or am I misunderstanding
| everything?
I would use remotable Presenter objects in .NET to allow the UI to consist
of the Presenter containing a real form View but linking that to remotable
Model and possibly Interactors.
|
Thanks Joanna.
Although I won't implement it right now, I'd like to think about some
underlines about this implementation.
At this moment, the only (or at least the biggest) issue is the server
notifications, like events from model or from the server side of the
presenter, that should be listened by client components, like views.
Afaics this is a small problem inside a lan, but inside a man or a wan,
how could these events be handled?
--
Joao Morais |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
