Application structure

[Chandrashekhar Mullaparthi]

Hi,

OTP has it's own Package system similar to what you find in Java - which
provides a namespace for your code, so that names of modules don't clash
with the names of modules in applications developed by someone else.

A crude comparison is that an application is similar to a library when using
C, C++ - it's a collection of code which implements certain functionality. 

You could call a collection of interoperting nodes a "system" - though it is
not official :-) 
You are right about the "node"

cheers
Chandru

-----Original Message-----
From: Walter C. Reel III [mailto:blitzfeuer@REDACTED]
Sent: 17 April 2003 23:51
To: erlang-questions@REDACTED
Cc: Ulf Wiger
Subject: Re: Application structure


Many thanks.  That pointed me in a much better direction.

On Thursday 17 April 2003 01:21 pm, Ulf Wiger wrote:
>
> 1) File structure
>
> Organize your code into App/src, App/ebin, etc.
> Try to keep the organization symmetric, e.g.
> MyLib/App1
>      /App2

I've noticed (after you mentioned it) that the standard libraries in the OTP

distribution adhere to that same type of organization.  Although I may be 
stretching it, would it be safe to say that applications closely resemble
the 
idea of a package in Python or Java?

So, just to make sure I understand the terminology, a "system" is a
collection 
of interoperating nodes (which could be running on different machines) and a

"node" is an instance of the Erlang VM which could host multiple 
application/server/etc. processes.  Right?
(Of course my current place of employment uses those terms but with
completely 
different meanings ;)

Cheers,
 - Walt



 NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  If you have received
this email in error please notify the sender immediately and delete this
email from your system without copying or disseminating it or placing any
reliance upon its contents.  We cannot accept liability for any breaches of
confidence arising through use of email.  Any opinions expressed in this
email (including attachments) are those of the author and do not necessarily
reflect our opinions.  We will not accept responsibility for any commitments
made by our employees outside the scope of our business.  We do not warrant
the accuracy or completeness of such information.