|
|
| Author |
Message |
|
| phicarre |
Posted: Mon Mar 23, 2009 6:52 pm |
|
|
|
User
Joined: 23 Mar 2009
Posts: 14
|
I am beginner and I don't master all notions of this language. I know I must read and read and ... read.
I would like to realize an "application" which interface machines on networks. As their protocols of communication is different, I suppose I must developp one "server" by manufacturer. I want to handle parallel connections.
Each "server" will have a parser for decoding the messages. Each server shall send information to a database (mysql)
One "server" could be between the servers and the database.
Finally, a "supervision" shall manage all these things.
How to structure this description (just a skeleton) in order to be the most efficient (best response time, distributed or not servers, no lost of messages, no blocking, etc ... ? |
|
|
| Back to top |
|
| uwiger |
Posted: Mon Mar 23, 2009 10:24 pm |
|
|
|
User
Joined: 03 Jul 2006
Posts: 604
Location: Sweden
|
phicarre wrote: I would like to realize an "application" which interface machines on networks. As their protocols of communication is different, I suppose I must developp one "server" by manufacturer. I want to handle parallel connections.
Each "server" will have a parser for decoding the messages. Each server shall send information to a database (mysql)
One "server" could be between the servers and the database.
Finally, a "supervision" shall manage all these things.
I think you should get a copy of Joe Armstrong's book "Programming Erlang".
Most of the above is explained in there. For the mysql interface, you can look at the ODBC component in OTP. |
|
|
| 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 can attach files in this forum You can download files in this forum
|
|
|