Ha - yeah how long ago would a machine like that have not been
"resource constrained" ! :)
But if it really is resource consttrained, some kind of static code
generation and pre compilation could help. Such tricks aren't uncommon
for phones, for instance.
Sent from my phone.
On 13/08/2009, at 11:21 PM, mrhoden(a)franklinamerican.com wrote:
Depending on your number of rules and facts, that amount of memory
will likely be a concern. If I had memory requirements like that I
would honestly look a clips.
-Michael
On Aug 13, 2009, at 2:19 AM, Thomas Frenken <Thomas.Frenken(a)offis.de>
wrote:
> Hello,
>
> I am interested in running Drools 5 (and especially Drools Fusion)
> on a
>>> somehow<< resource-constrained device for which only a J2SE 1.4 VM
>>> ist
> available.
>
> Since Drools meanwhile requires J2SE 1.5 I thought about backporting
> it.
> But before I invest so much effort, I got two questions:
>
> 1) I have downloaded the sourcecode. At a first glance the only
> reason for
> requiering J2SE 1.5 is the extensive use of generics. In case I would
> remove all generics from the code, would it be possible to compile
> drools
> for a J2SE 1.4 VM runtime in general or are there other more hidden
> reasons for requiering J2SE 1.5?
> 2) I already meantioned I am planning to run drools on a >>somehow<<
> resourcen-constrained device. I explicitly used the term >>somehow<<
> because I am talking of a device with a 400 Mhz CPU and 256 MB RAM
> (some
> people might laugh about calling this resource-constrained). How
> about
> resource-consumption of drools? Has anyone run drools on a device
> with
> similar resources?
>
> Thanks in advance!
>
> Best Regards
> Thomas Frenken
>
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-dev
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev