RE: Server side objects-if attributes/methods are addedis

Question

Hi Richard,
in addition to Peter Sham's mail you might have a
look at tech note N 11545. The subject is different
but you will see how to implement 'anchored'
objects(use proxies) or reference partitions. If your
server object project is a supplier plan to the
client I am afraid you have to redeploy client
whenever you change something on server. So probably
you have to change the way client and server
interact. One or two months ago there was discussion
of how to separate client from server. The subject
was something like how to avoid "bloated clients".
Regards,
Rumen
Hi,
You can deploy your server-side objects as server
using "Configure As"
in
Forte Workshop. Then all your client can >use"Reference Partition" to
reference your SO's on the server. Any change onthe >server-side logic
won't
require you re-deploy your clients.
But if there is object which will pass from serverto >client and no
matter
what the change is, you will need to re-deploymentof >your client
otherwise,
you will get a "deserialization" error. Bear inmind >that Forte deploy
all
the code ( like object structure, logic, etc ) to
your client during
deployment, only the data get passes through. Hence, >if there is any
change
in an object that will copy from server to client,
you have to update
the
"code" in your client too, that means, re-deploying
your client. The
only
way to get arround this is to "anchore" your object?>to the server, so
that
your client only gets a proxy of the object. Aslong >as you are adding
in
new things, I guess it ok. But there is a lot of
issues following
"archored"
object.
Hope this help.
Regards,
Peter Sham.
"Robinson, Richard" wrote:
Subject says is all. We have a situation wherewe'd like to avoid
rebuilding/redeploying the client side when aserver object is changed
(i.e., a new method or attribute is changed) or anobject that is
passed
from the server to a client is changed but theclient won't use the
new
methods/attributes.
Thanks in advance_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

Answer 1

Hi,
You can deploy your server-side objects as server using "Configure As" in
Forte Workshop. Then all your client can use "Reference Partition" to
reference your SO's on the server. Any change on the server-side logic won't
require you re-deploy your clients.
But if there is object which will pass from server to client and no matter
what the change is, you will need to re-deployment of your client otherwise,
you will get a "deserialization" error. Bear in mind that Forte deploy all
the code ( like object structure, logic, etc ) to your client during
deployment, only the data get passes through. Hence, if there is any change
in an object that will copy from server to client, you have to update the
"code" in your client too, that means, re-deploying your client. The only
way to get arround this is to "anchore" your object to the server, so that
your client only gets a proxy of the object. As long as you are adding in
new things, I guess it ok. But there is a lot of issues following "archored"
object.
Hope this help.
Regards,
Peter Sham.
"Robinson, Richard" wrote:
Subject says is all. We have a situation where we'd like to avoid
rebuilding/redeploying the client side when a server object is changed
(i.e., a new method or attribute is changed) or an object that is passed
from the server to a client is changed but the client won't use the new
methods/attributes.
Thanks in advance
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]