|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
AMF3 referencesHi Guys,
I'm running into some issues with SabreAMF regarding object and string references.. Way back I made a change to maintain the class definition/object references across multiple bodies; because of a bug I encountered.. Now I'm looking at a bug report, which has the reverse problem.. but for string references.. So, the logical conclusion is that object and class references are maintained across AMF3 bodies, but strings aren't... This, however, seems so weird though.. It made me wonder how you guys deal with this... Are your object and class references maintained across bodies? Evert |
|
|
Re: AMF3 referencesHi Evert,
Afaik, AMF3 references are cleared for all types (strings, classes & objects) at the end of each 'context'. This includes the remoting header (a gotcha for me) and each body, which is a really odd design choice, because the whole idea of references is to cut down the bytes sent down the wire .. Hope that helps sort your problem! Cheers, Nick On 24 Mar 2008, at 22:08, Evert | Rooftop wrote: > Hi Guys, > > I'm running into some issues with SabreAMF regarding object and string > references.. > > Way back I made a change to maintain the class definition/object > references across multiple bodies; because of a bug I encountered.. > Now I'm looking at a bug report, which has the reverse problem.. but > for > string references.. > > So, the logical conclusion is that object and class references are > maintained across AMF3 bodies, but strings aren't... > > This, however, seems so weird though.. It made me wonder how you guys > deal with this... > > Are your object and class references maintained across bodies? > > Evert > _______________________________________________ > PyAMF dev mailing list - dev@... > http://lists.pyamf.org/mailman/listinfo/dev |
|
|
Re: AMF3 referencesThanks a lot! I'll reiterate my test cases, just wanted to know I'm not
crazy Nick Joyce wrote: > Hi Evert, > > Afaik, AMF3 references are cleared for all types (strings, classes & > objects) at the end of each 'context'. This includes the remoting > header (a gotcha for me) and each body, which is a really odd design > choice, because the whole idea of references is to cut down the bytes > sent down the wire .. > > Hope that helps sort your problem! > > Cheers, > > Nick > > > > On 24 Mar 2008, at 22:08, Evert | Rooftop wrote: > > >> Hi Guys, >> >> I'm running into some issues with SabreAMF regarding object and string >> references.. >> >> Way back I made a change to maintain the class definition/object >> references across multiple bodies; because of a bug I encountered.. >> Now I'm looking at a bug report, which has the reverse problem.. but >> for >> string references.. >> >> So, the logical conclusion is that object and class references are >> maintained across AMF3 bodies, but strings aren't... >> >> This, however, seems so weird though.. It made me wonder how you guys >> deal with this... >> >> Are your object and class references maintained across bodies? >> >> Evert >> _______________________________________________ >> PyAMF dev mailing list - dev@... >> http://lists.pyamf.org/mailman/listinfo/dev >> > > _______________________________________________ > PyAMF dev mailing list - dev@... > http://lists.pyamf.org/mailman/listinfo/dev > |
| Free embeddable forum powered by Nabble | Forum Help |