As has been stated already, storing an instance of Transfer in the session is a terrible idea, unless you enjoy crippled servers for breakfast, lunch, dinner, and in-between-meal snacks. Presumably you have a finite number of datasources that you are dealing with in your application, rather than literally one per user. If that is the case, I would recommend something along the lines of the following:
1) create named instances of Transfer - one for each datasource - and set them into the application scope 2) set a session variable for each user that contains the name of the appropriate Transfer instance 3) when you need to get at Transfer, call application[session.transferInstance] HTH
-- Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en
