Re: help With API

Fri, 07 Jul 2006 14:22:24 -0700

** Nice, bring John C. in to the mix =)

On 7/7/06, McKenzie, James J C-E LCMC HQISEC/L3 <[EMAIL PROTECTED] > wrote:
**

Tim:

I agree with your assessment of the underlying software requirements to get either a Java 'application' or a C# 'application' to run with ARS.

As far as bloatware, take a look at the space requirements for Office.  Each release has seen growth in the disk and memory space needed to run it.  This is what Dvorak and others see as 'bloatware'.  I remember the days of 'overlays' or the need to 'compartmentalize' your program so that a stub would stay in memory and portions of your program were swapped in and out of memory.  Now this is done through the use of dynamic libraries and such.  In any case, with the growth has come increased functionality and some very good 'looking' software.  Plus, isn't it software that drives the need for 'bigger, better' hardware?

Or just what are those college aged folks filling up there hard drives with?  It is not mp3's and prirated movies by themselves.

James McKenzie
 

-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tim Widowfield
Sent: Friday, July 07, 2006 9:12 AM
To: arslist@ARSLIST.ORG
Subject: Re: help With API

 Er... Um...   C# == "the C that Microsoft makes"?   More like the Java-clone that Microsoft "invented."

Lest anyone think you can compile a C# Remey API program into a standalone .exe file, you should be aware that you will need the .NET equivalent of JNI helper files.  They include:

    ATLWrappers.dll
    Interop.ATLWRAPPERSLib.dll
    DotNet.dll
    DotNet.tlb
    DotNet.xml

These "helper" files will allow your compiled .NET bytecode to talk to Remedy's native, unmanaged API DLLs.

As far as the "bloatware" label, well let's take a look.  We'll right-click on the folder named C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727, then select Properties.  What do we see?  The size on disk is a little over 88 MB.  The JDK is about the same size, maybe a little less.

Don't get me wrong.  I like C#.  But in the Remedy world, at least, we're in the same boat.  We have to rely on bridge software to tap into the native libraries. 

 
Tim Widowfield
[EMAIL PROTECTED]
v: 937-878-9045
f: 937-878-9055
m: 937-369-7012
http://www.widowfield.com
 
----- Original Message ----
From: "McKenzie, James J C-E LCMC HQISEC/L3" 
To: arslist@ARSLIST.ORG
Sent: Friday, July 7, 2006 10:45:28 AM
Subject: Re: [ARSLIST] help With API
 
RE: help With API**         Tim: 
  Its like this:  Lettuce.  That is what Java is.  Pure Java is like radinnicinco.  So when you give me Iceberg lettuce, yes it is lettuce but I don't like it.  Some folks think that their Java JNI code is actually Java, but it will not work without external help.  Thus the need for Java API "interfaces" which actually call 'c' API function calls.  This is why some folks have actually given up on Java and moved onto C# (yes folks the C that Microsoft makes.)  What I would like to see is a Pure Java implementation of some of the products.  Why?  Not everyone runs Windows/Solaris and actually NEED to run "something" against our beloved Remedy ARS.

  So, it is either build something from 'c' code or implement in Java WITHOUT running a JNI interface.  Get the point?  Calling something "Java" does not necessarily mean "Write Once, Run Everywhere".  And if you want bloatware, Java takes the cake.

  James McKenzie  
  -----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Tim Widowfield
Sent: Friday, July 07, 2006 7:39 AM
To: arslist@ARSLIST.ORG
Subject: Re: help With API
  Oh, gee.  Now we're all on pins and needles.  So these things that I've been compiling with .java extensions, these classes that I run in the JVM -- if they're not Java, what exactly *are* they, James? 

    
Look, it's like saying anything that isn't managed code isn't .NET.  It's illogical.  Sun had hoped that JNI would serve as a bridge between legacy code and pure Java implementations.  I'm afraid some organizations will never get around to phase two (viz., dump that legacy code).  But that doesn't mean it isn't Java. 

    
"Write once, run anywhere" is a nice marketing slogan, and it's certainly a laudable goal, but it is not an exclusively defining characteristic. 

    
   
Tim Widowfield
[EMAIL PROTECTED]
v: 937-878-9045
f: 937-878-9055
m: 937-369-7012 
http://www.widowfield.com  
  
----- Original Message ---- 
From: "McKenzie, James J C-E LCMC HQISEC/L3"   
To: arslist@ARSLIST.ORG
Sent: Friday, July 7, 2006 10:17:08 AM 
Subject: Re: [ARSLIST] help With API  
  
RE: help With API**         Axton:   
  You are correct.  My statement was:   
  If it is a Java program, then it should run anywhere.  This is obviously not a Java application.   
  James McKenzie    
  -----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton Grams
Sent: Thursday, July 06, 2006 8:37 PM
To: arslist@ARSLIST.ORG
Subject: Re: help With API 
  Java JNI wrappers require the native c libs for each platform.   
  Axton Grams 
  McKenzie, James J C-E LCMC HQISEC/L3 wrote:   
> **
>    
> Carey:   
>    
> You stated Java application...That means it should work on a Mac,    
> Solaris, Windows, even my Java based phone.  If it is not so, then it    
> is technically not Java.   
>    
> James McKenzie
>    
> -----Original Message-----   
> From: Action Request System discussion list(ARSList)     __20060125_______________________This posting was submitted with HTML in it___

Reply via email to