Missing conventions and documentation for typical use case - client-server application.

[DartBot]

This issue was originally filed by [email protected]

---

Issue/feedback:
A documentation covers a use case when Dart works as client-side application within browser, but a typical use case and one of the most powerful Dart feature is client-server orientation - this means that Dart can replace say PHP on server side and JavaScript on client side.

So we need to see how a typical client/server application must look like. The following links:
http://pub.dartlang.org/doc/package-layout.html
http://pub.dartlang.org/doc/glossary.html
don't provide such information. I didn't find any such info on http://dartlang.org too.

So it would be useful to define and describe the following:

1. Where the entry point file for server-side application must be placed, for example server.dart file? What is relation of server-side entry-point with client-side entry point?
2. Where packages of the server-side application must be placed that will use (import) other library packages? For example:
   app/my_package1
   app/my_package2
   etc.
   or any other directory (conventions required here).
3. How can we import server-side packages from my entry-point file?
4. Question of interaction between server side-packages and client side packages. We need to know how server-side packages can interact with client-side packages in Dart.
5. Interaction between server-side packages using some event system (event package).

Thanks.

[DartBot]

This comment was originally written by [email protected]

---

There is a typo here:

1. How can we import server-side packages from my entry-point file?
   must be replaced with:
2. How can we import server-side packages from the entry-point file?

I would like also clarify about the 5. item:

1. Interaction between server-side packages using some event system (event package).
   By the 'event' package I mean some package that will provide event system for other packages so that packages will be able to subscribe on some event and a package will be able to trigger some event. May be such 'event' package is not necessary at all but it can be convinient to have working system of interaction between packages out of box.

[kwalrath]

Removed Area-Documentation label.
Added Area-Site label.

[nicolasgarnier]

This issue has been moved to Github as part of a migration. Please use the Issue on Github going forward: https://github.com/dart-lang/dartlang.org/issues

---

Added MovedToGithub label.