|
|
| Author |
Message |
|
| dsmith |
 Posted: Wed Aug 08, 2007 8:34 pm |
 |
|
|
User
Joined: 08 Aug 2007
Posts: 41
Location: Toronto
|
I was wondering if anyone has heard of an Erlang browser plug-in. (any browser)
I saw some posts in the erlang.org archive from 2003 discussing this. Has anyone thought about what it would take to address the security issues? (sandbox-erlang) |
|
|
| Back to top |
 
|
| francesco |
| Posted: Thu Aug 09, 2007 9:39 am |
|
|
|
User
Joined: 07 Jul 2006
Posts: 249
Location: London
|
I think the talks you saw in 2003 remained in conceptual state. Erlang was built for server side applications, and that is where its strengths lie. It has always been weak on the client side (see discussions on GS in another forum).
Regarding Safe Erlang, a thesis project was done at the computer science laboratory (The birthplace of Erlang) back in 1996. The URL is http://user.it.uu.se/~gaffe/general/safe/
Based on the above, the Australian Defence Fore Academy did some work as well which you should find interesting. The link is http://www.adfa.oz.au/~lpb/research/sserl/
Francesco
--
http://www.erlang-consulting.com |
|
|
| Back to top |
|
| dsmith |
| Posted: Sat Aug 11, 2007 1:08 am |
|
|
|
User
Joined: 08 Aug 2007
Posts: 41
Location: Toronto
|
I'm aware that Erlangs strengths suit it for highly concurrent server apps. This is what I'm primarily interested in.
Let me explain. I work in the financial industry on distributed business application with a large user base. Our current architecture is an SOA with an MQ middleware. The architecture is fine for electronic processing, but online user experience for our internet/intranet based systems is very weak, primarily because the quite coarse grained services (lots of business edits) can't provide immediate feedback to the user, and writing fine grained services results in a very chatty system which the current architecture can't deal with.
My goal is to prototype a server application, written in Erlang, which is able to process a high volume of business constrains, and serve the results back to a browser quickly.
Although we might try to keep all edits on the server side, there has always been those edits (such as date range constraints, and phone number pattern constraints) that always end up implemented on the browser as well. This usually means writing the rule twice, once in Javascript and once in the servers language. This was the motivation for my original question. |
|
|
| Back to top |
|
| francesco |
| Posted: Mon Aug 13, 2007 9:16 am |
|
|
|
User
Joined: 07 Jul 2006
Posts: 249
Location: London
|
The closest we have come to what you are doing at Erlang Training and Consulting is to integrate server side LYME (Linux, Yaws, Mnesia & Erlang) applications with Ajax in the front-end. The conclusion was to stay clear of applications such as backbase and go for the simple standalone widgets. Both for the sanity and morale of the developers. Examples of Erlang and AJAX integration are available in this contribution:
http://forum.trapexit.org/viewtopic.php?t=6695
Regards,
Francesco |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
