|
Home > Archive > Macromedia Flash Server > April 2005 > Help with proxied shared objects - when can I start
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Help with proxied shared objects - when can I start
|
|
| Robert Laing 2005-04-26, 7:45 am |
| Apologies=20for=20the=20long=20post=20-=20it=20just=20takes=20a=20while=20=
to=20explain..!
I=20have=20numerous=20'secondary'=20appl
ication=20instances=20all=20retrie=
ving=203=20proxied=20shared=20objects=20
from=20the=20default=20application=
=20instance. =20One=20of=20the=20proxied=20shared=20o
bjects=20is=20non-pers=
istent=20and=20therefore=20the=20seconda
ry=20application=20instance=20alwa=
ys=20receives=20an=20onSync=20event=20on
ce=20the=20proxied=20shared=20obje=
ct=20has=20been=20received. =20However,=20the=20other=202=20proxied=
20share=
d=20objects=20are=20persistent=20and=20i
f=20the=20shared=20object=20hasn't=
=20changed=20the=20secondary=20applicati
on=20instance=20never=20receives=20=
an=20onSync=20event=20from=20the=20defau
lt=20application=20instance.
So,=20without=20the=20onSync=20event=20I
=20don't=20know=20when=20to=20star=
t=20working=20with=20the=20shared=20obje
ct.=20It=20could=20be=20that=20the=
=20shared=20object=20is=20correct=20in=2
0the=20secondary=20application=20i=
nstance=20or=20it=20could=20be=20that=20
the=20shared=20object=20just=20has=
n't=20sync'ed=20up=20yet=20-=20I=20simply=20don't=20know.
I=20do=20receive=20a=20NetConnection=20o
nStatus=20code=20of=20SharedObject=
..Proxy. Connect,=20but=20the=20information=20tha
t=20comes=20with=20this=20s=
eems=20limited. =20I'm=20assuming=20this=20message=20com
es=20through=20when=
=20the=20secondary=20application=20insta
nce=20has=20figured=20out=20that=20=
it's=20copy=20of=20the=20proxied=20share
d=20object=20is=20the=20same=20as=20=
the=20one=20it=20connects=20to. =20However,=20nowhere=20in=20the=20info=
20o=
bject=20does=20it=20say=20which=20shared
=20object=20its=20talking=20about,=
=20so=20since=20I=20have=203=20shared=20
objects=20getting=20an=20arbitrary=
=20message=20about=20one=20of=20them=20b
eing=20the=20same=20(but=20not=20t=
elling=20me=20which=20one)=20is=20no=20h
elp=20at=20all.
The=20books=20I've=20read=20say=20always
=20wait=20for=20the=20onSync=20eve=
nt=20- =20which=20I=20sometimes=20never=20recei
ve.=20So=20what=20is=20the=20=
best=20way=20to=20reliably=20deal=20with
=20a=20proxied=20shared=20object=20=
and=20always=20know=20that=20it=20is=20t
here=20before=20doing=20anything=20=
with=20it? =20Any=20help=20would=20be=20gratefully=
20appreciated.
This=20e- mail=20and=20any=20attached=20files=20ar
e=20for=20the=20exclusive=
=20use=20of=20the=20addressee=20and=20ma
y=20contain=20privileged=20and/or=20=
confidential=20information.=20If=20you=20receive=20this=20e-mail=20in=20er=
ror=20you=20should=20not=20disclose=20th
e=20contents=20to=20any=20other=20=
person=20nor=20take=20copies=20but=20sho
uld=20delete=20it=20and=20telephon=
e=20us=20immediately=20on=20+44(0)20=207
440=201100.
TEQUILA\=20London=20Limited=20does=20not
=20make=20any=20warranty=20as=20to=
=20the=20accuracy=20or=20completeness=20
of=20this=20e-mail=20and=20we=20ac=
cept=20no=20liability=20for=20its=20cont
ent=20or=20use.=20Any=20opinions=20=
expressed=20in=20this=20e- mail=20are=20those=20of=20the=20author=2
0and=20d=
o=20not=20necessarily=20reflect=20the=20
opinions=20of=20TEQUILA\=20London=20=
Limited.
TEQUILA\=20London=20Limited=20operates=2
0within=20the=20parameters=20set=20=
by=20the=20Data=20Protection=20Act=20199
8=20with=20regard=20to=20the=20use=
=20of=20personal=20information=20includi
ng=20e-mail=20addresses.=20We=20ac=
cept=20no=20liability=20for=20the=20forw
arding=20of=20this=20e-mail=20to=20=
other=20parties=20that=20may=20result=20
in=20unsolicited=20e-mails=20being=
=20received=20by=20those=20whose=20email
=20addresses=20appear=20in=20this=20=
e-mail.
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
| |
| Brian Lesser 2005-04-26, 5:45 pm |
| Hi Robert,
I think you've found a problem in the way persistent shared objects are
handled on the server. It would be OK if you could create a
SharedObject.onStatus method that would receive the
SharedObject.Proxy.Connect message but that doesn't seem to work.
Therefore when you have any persistent proxied shared object(s) I don't
see how you can do anything but wait for n SharedObject.Proxy.Connect
messages before writing to a server-side persistent proxied shared
object. (Where n is the total number of temporary and proxied shared
objects.)
Yours truly,
-Brian
Robert Laing wrote:
>Apologies for the long post - it just takes a while to explain..!
>
>I have numerous 'secondary' application instances all retrieving 3 proxied shared objects from the default application instance. One of the proxied shared objects is non-persistent and therefore the secondary application instance always receives an onSyn
c event once the proxied shared object has been received. However, the other 2 proxied shared objects are persistent and if the shared object hasn't changed the secondary application instance never receives an onSync event from the default application ins
tance.
>
>So, without the onSync event I don't know when to start working with the shared object. It could be that the shared object is correct in the secondary application instance or it could be that the shared object just hasn't sync'ed up yet - I simply don't
know.
>
>I do receive a NetConnection onStatus code of SharedObject.Proxy.Connect, but the information that comes with this seems limited. I'm assuming this message comes through when the secondary application instance has figured out that it's copy of the proxie
d shared object is the same as the one it connects to. However, nowhere in the info object does it say which shared object its talking about, so since I have 3 shared objects getting an arbitrary message about one of them being the same (but not telling m
e which one) is no help at all.
>
>The books I've read say always wait for the onSync event - which I sometimes never receive. So what is the best way to reliably deal with a proxied shared object and always know that it is there before doing anything with it? Any help would be gratefully
appreciated.
>
>This e-mail and any attached files are for the exclusive use of the addressee and may contain privileged and/or confidential information. If you receive this e-mail in error you should not disclose the contents to any other person nor take copies but sho
uld delete it and telephone us immediately on +44(0)20 7440 1100.
>
>TEQUILA\ London Limited does not make any warranty as to the accuracy or completeness of this e-mail and we accept no liability for its content or use. Any opinions expressed in this e-mail are those of the author and do not necessarily reflect the opini
ons of TEQUILA\ London Limited.
>
>TEQUILA\ London Limited operates within the parameters set by the Data Protection Act 1998 with regard to the use of personal information including e-mail addresses. We accept no liability for the forwarding of this e-mail to other parties that may resul
t in unsolicited e-mails being received by those whose email addresses appear in this e-mail.
>
>=---------------------------------------------------------
>Supported by Fig Leaf Software - http://www.figleaf.com
>=---------------------------------------------------------
>
>To change your subscription options or search the archive:
>http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>
>
--
________________________________________
______________________________
Brian Lesser
Assistant Director, Teaching and Technology Support
Computing and Communications Services
Ryerson University
350 Victoria St.
Toronto, Ontario Phone: (416) 979-5000 ext. 6835
M5B 2K3 Fax: (416) 979-5220
Office: AB48D E-mail: blesser-6s6ziW1YCwCw5LPnMra/2Q@public.gmane.org
(Enter through LB66) Web: http://www.ryerson.ca/~blesser
________________________________________
______________________________
=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
|
|
|
|
|