That's a good point.  Maybe yours is already the best approach:  embed J in a 
popular and widely-distributed technology stack (.NET in your case) and defer 
all the "standard stuff" to the popular, mature tools that everyone is already 
used to.  No use re-inventing the wheel. 

We still need a way to let the J developer express the interface and semantics 
of his application so that .NET can expose it as a WS, but that's a much 
smaller bite.


-Dan

Please excuse typos; composed on a handheld device.

On Apr 24, 2013, at 8:08 PM, Greg Borota <[email protected]> wrote:

> About implementing it in J, I can't speak much, I am still picking up the
> basics of J. But I guess it's a huge effort, if you want something that can
> be hit by at least hundreds of users concurrently... Because you'd have to
> implement functionality that currently comes out of the box with the web
> servers (apache, iis, etc.) My proof of concept WS returns to me results
> instantly. But jhs (at least on my machine) takes too long, and that's just
> one user hitting it...
> 
> 
> On Wed, Apr 24, 2013 at 6:14 PM, Dan Bron <[email protected]> wrote:
> 
>> I am thinking of making J interoperability seamless and transparent.  It
>> will make it easier to embed J on the server-side if we make its interface
>> familiar and standard, and in the current state of the IT world, that means
>> web services.
>> 
>> A WS interface will allow us to use modern frontend toolkits to write
>> user-facing (browser-based) apps, e.g. in Flash, Silverlight, or more
>> likely in days to come, HTML5.
>> 
>> It'll also make it easier to offer headless J-based services into IT
>> depts, with leas of the usual friction we encounter when presenting a new,
>> (extremely) unfamiliar language.
>> 
>> In short, it lets us express ourselves in the way we prefer (i.e. J code)
>> while allowing the outside world to interact with us in the way they prefer
>> (i.e. web services).
>> 
>> For this to work, I shine the WS interface has to be implemented natively
>> in J; if we require a (specific) technology stack, we risk igniting the
>> kind of holy war we are specifically tying to avoid.
>> 
>> -Dan
>> 
>> Please excuse typos; composed on a handheld device.
>> 
>> On Apr 24, 2013, at 3:46 PM, Greg Borota <[email protected]> wrote:
>> 
>>> Dan, do you mind giving details on what you have in mind? I quickly
>>> hacked-up a .NET based restful service during my lunch time. It has 2
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to