| Newsgroups |
perl.p5ee |
| Message-ID |
<[email protected]> |
On Wed, May 15, 2002 at 10:38:57AM -0400, Stephen Adkins wrote:
> At 11:38 AM 5/15/2002 +0200, [email protected] wrote:
> ...
> >The problem simply is that people give p5ee different priorities. I don't
> >volunteer as well. I once wrote you a mail that I'd think that the whole
> >concurrency stuff is not getting thought about. You replied that I should
> >do it then. But that won't work, since I don't have the time for this right
> >now. Anyway, that doesn't erase the need to work on it. So you will have
> to do
> >it if noone else does :/
> ...
> >Torvald
>
> Hi,
>
> I looked back at your earlier messages to try to understand what you
> are suggesting needs to be thought about or accounted for more.
>
> Date: Tue, 5 Feb 2002 13:18:09 +0100
> http://archive.develooper.com/p5ee%40perl.org/msg00710.html
> There is almost no talk about architecture (in this big scale) on the list.
> Maybe all but me know already how it should look like, but I doubt this.
> You are not touching the big and hard parts like:
> -concurrency
> -object models
> -distributed applications (running the same program at several places)
> -specification/verification of programs
>
> Date: Tue, 5 Feb 2002 19:50:25 +0100
> http://archive.develooper.com/p5ee%40perl.org/msg00715.html
> Analysis isnt done yet (see above), design even less, what should we do with
> code ??? How should anyone start developing something, if there is no
> agreement on the basic facts ? How to handle shared data in a distributed
> setup? How to address objects? The list goes on and on ...
>
> When you speak about Concurrency, are you speaking about transactions?
> locking? synchronization? multi-threading?
> I am thinking about all these things.
Well, I think there is a need for concurrency. But IIRC there has been no
analysis of the required type/amount/.. of concurrency yet. So we don't
really know which problem space we try to address. Concurrency on which
layer, how are the components distributed, which guarantees are needed,
etc.
When we know that, we can try to solve it with means like transactions,
msg queues, whatever.
> Please describe a system that is facing the concurrency issues that you
> are concerned with. Then I can address how is would be handled in the
> framework.
I know what I'd like to use. But I don't know what you need. So I don't
really have to solve a specific problem (since I'm not earning money for
any related projects or the like), but I can see that other people will
want concurrency in some way and that would mean a lot of work for them.
Or it wouldn't work at all.
Torvald