On 03/28/2013 04:34 PM, Roger wrote:
> Hi All,
>
> I think keeping the idea of writing json to standard out is a good one.
>
> The question of how we implement the one we need initially is harder.
> (These will serve as samples for the community).
Exactly.
>
> I think of c# as a language. I see that there are several ways to
> use as a scripting language out there. There is windows scripting host
> for java and vb script, I saw an interesting reference to ironpython.
> I think all of these work if they write json out.
C# is a language - an interpreted language - like Python, or Perl, or
the shell - just microsoftie...
One consideration is that everything we do might wind up installed on
100K machines. So, we want to try hard to stick to something that's
already on as many machines as possible. It's my understanding that C#
would be on most or all machines out there, since it's commonly used
with .net. It's my understanding VBscript has been end-of-lifed by
Microsoft - or I might have suggested that.
> I plan to look into this more and try to implement a sample soon.
You might touch bases with Charles Hanes (CCed on this note). I think
he has similar thoughts.
--
Alan Robertson <[email protected]> - @OSSAlanR
"Openness is the foundation and preservative of friendship... Let me claim
from you at all times your undisguised opinions." - William Wilberforce
_______________________________________________
Assimilation mailing list - Discovery-Driven Monitoring
[email protected]
http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
http://assimmon.org/
