I'm trying to port Rhino-Queues to the compact framework (cf). At the moment I see some major problems:
- esent and is not available on Windows CE - rq is tied to esent, there is no abstraction of the storage engine - CF has no System.Transactions - Mutex.Pulse and some other stuff around Threading is not available on CF At the moment I'm stuck at the decision, how to continue with my effort. Is see two different ways: 1. Building a RQ - compatible client for the CF and stripping out esent, system.transactions etc. This would result in a complete rework with only some similarities in the codebase. 2. Try to introduce abstractions to rq to exchange the storage engine etc. What do you think? Any ideas? Let us keep in mind, that there are other platforms we could target (mono, silverlight). Louis -- You received this message because you are subscribed to the Google Groups "Rhino Tools 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/rhino-tools-dev?hl=en.
