Well, the only change I would make to your discussion is not wrapping the C API, but instead the Java API. The Java API is the one that BMC is moving forward with, I mean, they rewrote the entire Server in Java....so....I could see having the API available in a scripting language. Now...I don't know Node.js, so I can't speak to it specifically, and I know that Java and JavaScript aren't the same, but I can't imagine them being too awfully hard to marry together for scripting purposes. Most of the wrappers, as I understand them, have been community efforts, or individual efforts inside BMC that never got released 'supported'...which means they were essentially all unsupported...so...start a GitHub project or something and see how much traction it gets :)
On Tue, Oct 11, 2016 at 1:54 PM, Andrew Hicox <and...@hicox.com> wrote: > ** > > Yeah REST was my first inclination ... I mean you're in javascript > already, getting and putting json encoded messages on a network is > obviously the path of least resistance. > > However. There are lots of things on the C API that aren't exposed via > REST ... for instance, form/object definition stuff ... tunnelling direct > sql to the DB ... lots of things really. Not to mention the tremendous > utility of just being able to cut every other damn thing out of the > equation and connect directly to the arserver and do what needs to be done! > > Having to pound out C when you need that stuff is a pain (and time > prohibative). Having the full(ish) API exposed in a scripting environment > is HUGE, and pretty much the only reason I still use Perl. And I do ... > literally every single day on the job. That toolkit is simply indispensable. > > In fact, I can say without a doubt, that being able to pull that rabbit > out of my hat when needed, has pretty much made a career for me at this > point. > > However, Perl is old, and it is dying. > > We need a new platform for this functionality (and if it's going to be a > community effort like ARSPerl, we need to attract younger developers to > keep it alive). > > I strongly believe node.js is to 2016 as perl was to 1996. This is where > the action is, and it is where we need the ARS API to be. > > Granted, the REST stuff is great. You shouldn't NEED the full on API to do > row operations, and this fills that gap nicely. You can do a whole lot with > it, no doubt. > > However, sometimes you DO need the whole shebang, and having it at your > fingertips ... in the same environment where you have literally everything > else at your fingertips as well ... from PDF renderers to full on GUI > frameworks like Cordova and Electron ... > > Yes. I could do this myself, given enough time and redbull. But then I've > got to worry about it breaking on new releases and yadda yadda. > > Really, it seems to me that it would be a brilliant move for BMC > themselves to publish an NPM module essentially porting the C API directly > into node.js > > Am I way out in lala land, or do others here agree? If there's interest, I > guess I could make a communities idea and hope it gets up votes enough to > get traction. > > -Andy > > On Oct 11, 2016 1:19 PM, "LJ LongWing" <lj.longw...@gmail.com> wrote: > >> ** >> Andy, >> As indicated by Thad, you should see in the near future interaction >> through Node.js into Remedy through the RestAPI. So, not the C like you >> indicated, but with Rest, this will give you similar access to Remedy that >> the ARSPerl did, in that ARSPerl was more interested in interacting with >> Remedy records than anything else, and the RestAPI gives you complete >> access to the full CRUD capability for record management. >> >> On Tue, Oct 11, 2016 at 11:36 AM, Thad Esser <thad.es...@gmail.com> >> wrote: >> >>> ** >>> Must be something in the air. I just went through some introductory >>> node.js training yesterday. The demo app they built used the http.get >>> method (https://nodejs.org/api/http.html) to call a REST API and showed >>> how to process the JSON that was returned. ARS 9.x has a REST API ( >>> https://docs.bmc.com/docs/display/public/ars91/BMC+Remedy+A >>> R+System+REST+API+overview), although I haven't worked with it >>> directly. >>> >>> Hopefully that helps in some way. >>> >>> Cheers, >>> Thad >>> >>> On Mon, Oct 10, 2016 at 7:18 PM, Andrew Hicox <and...@hicox.com> wrote: >>> >>>> ** Hello all, >>>> >>>> I know this is a little bit of a long shot, but my google-fu isn't >>>> turning up much. >>>> Does any one know of / have heard anything about hacking the ARS C API >>>> onto node.js (sort of like ARSPerl does for perl)? >>>> >>>> Lately I've been diving into node.js, and it occurs to me that I could >>>> pretty much replace a lot of my aging perl tools with snazzy new >>>> shenanigans ... >>>> >>>> -Andy >>>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>> >>> >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
