Feature request

View: New views
2 Messages — Rating Filter:   Alert me  

Feature request

by Marcel Apfelbaum :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi,

 

I use FlorineFx in order to transfer binary data from an Asp.Net server to a Flex3 client.

Most of the objects I transfer to client are saved on the server using the same binary serialization that Fluorine is using to transfer data to client.

 

My problem is that I have a lot of properties that I don't want to transfer to client side but are serialized anyway!

The only way I could handle it is to implement FluorineFx.AMF3.IExternalizable, but this is not so user friendly (to do it for every class!).

It is possible to add to FluorineFx a new attribute 'FluorineFx.AMF3.NotSerializable' to be added on every field/property we don't want to send to client?

 

Thank you,

 Marcel

  


_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesilentgroup.com

Re: Feature request

by Support-179 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Hi Marcel,
 
For properties and fields you can use the FluorineFx.TransientAttribute attribute
For fields (only) you can use System.NonSerializedAttribute too.
 
Zoli


From: fluorine-bounces@... [mailto:fluorine-bounces@...] On Behalf Of Marcel Apfelbaum
Sent: Monday, May 11, 2009 12:28 PM
To: fluorine@...
Subject: [Fluorine] Feature request

Hi,

 

I use FlorineFx in order to transfer binary data from an Asp.Net server to a Flex3 client.

Most of the objects I transfer to client are saved on the server using the same binary serialization that Fluorine is using to transfer data to client.

 

My problem is that I have a lot of properties that I don't want to transfer to client side but are serialized anyway!

The only way I could handle it is to implement FluorineFx.AMF3.IExternalizable, but this is not so user friendly (to do it for every class!).

It is possible to add to FluorineFx a new attribute 'FluorineFx.AMF3.NotSerializable' to be added on every field/property we don't want to send to client?

 

Thank you,

 Marcel

  


_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesilentgroup.com