ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent-MP/MP.pm
(Generate patch)

Comparing AnyEvent-MP/MP.pm (file contents):
Revision 1.44 by root, Wed Aug 12 21:39:58 2009 UTC vs.
Revision 1.53 by root, Fri Aug 14 15:31:21 2009 UTC

9 $NODE # contains this node's noderef 9 $NODE # contains this node's noderef
10 NODE # returns this node's noderef 10 NODE # returns this node's noderef
11 NODE $port # returns the noderef of the port 11 NODE $port # returns the noderef of the port
12 12
13 $SELF # receiving/own port id in rcv callbacks 13 $SELF # receiving/own port id in rcv callbacks
14
15 # initialise the node so it can send/receive messages
16 initialise_node; # -OR-
17 initialise_node "localhost:4040"; # -OR-
18 initialise_node "slave/", "localhost:4040"
14 19
15 # ports are message endpoints 20 # ports are message endpoints
16 21
17 # sending messages 22 # sending messages
18 snd $port, type => data...; 23 snd $port, type => data...;
19 snd $port, @msg; 24 snd $port, @msg;
20 snd @msg_with_first_element_being_a_port; 25 snd @msg_with_first_element_being_a_port;
21 26
22 # miniports 27 # creating/using ports, the simple way
23 my $miniport = port { my @msg = @_; 0 }; 28 my $simple_port = port { my @msg = @_; 0 };
24 29
25 # full ports 30 # creating/using ports, tagged message matching
26 my $port = port; 31 my $port = port;
27 rcv $port, smartmatch => $cb->(@msg);
28 rcv $port, ping => sub { snd $_[0], "pong"; 0 }; 32 rcv $port, ping => sub { snd $_[0], "pong"; 0 };
29 rcv $port, pong => sub { warn "pong received\n"; 0 }; 33 rcv $port, pong => sub { warn "pong received\n"; 0 };
30 34
31 # remote ports 35 # create a port on another node
32 my $port = spawn $node, $initfunc, @initdata; 36 my $port = spawn $node, $initfunc, @initdata;
33
34 # more, smarter, matches (_any_ is exported by this module)
35 rcv $port, [child_died => $pid] => sub { ...
36 rcv $port, [_any_, _any_, 3] => sub { .. $_[2] is 3
37 37
38 # monitoring 38 # monitoring
39 mon $port, $cb->(@msg) # callback is invoked on death 39 mon $port, $cb->(@msg) # callback is invoked on death
40 mon $port, $otherport # kill otherport on abnormal death 40 mon $port, $otherport # kill otherport on abnormal death
41 mon $port, $otherport, @msg # send message on death 41 mon $port, $otherport, @msg # send message on death
42 42
43=head1 CURRENT STATUS
44
45 AnyEvent::MP - stable API, should work
46 AnyEvent::MP::Intro - outdated
47 AnyEvent::MP::Kernel - WIP
48 AnyEvent::MP::Transport - mostly stable
49
50 stay tuned.
51
43=head1 DESCRIPTION 52=head1 DESCRIPTION
44 53
45This module (-family) implements a simple message passing framework. 54This module (-family) implements a simple message passing framework.
46 55
47Despite its simplicity, you can securely message other processes running 56Despite its simplicity, you can securely message other processes running
50For an introduction to this module family, see the L<AnyEvent::MP::Intro> 59For an introduction to this module family, see the L<AnyEvent::MP::Intro>
51manual page. 60manual page.
52 61
53At the moment, this module family is severly broken and underdocumented, 62At the moment, this module family is severly broken and underdocumented,
54so do not use. This was uploaded mainly to reserve the CPAN namespace - 63so do not use. This was uploaded mainly to reserve the CPAN namespace -
55stay tuned! The basic API should be finished, however. 64stay tuned!
56 65
57=head1 CONCEPTS 66=head1 CONCEPTS
58 67
59=over 4 68=over 4
60 69
61=item port 70=item port
62 71
63A port is something you can send messages to (with the C<snd> function). 72A port is something you can send messages to (with the C<snd> function).
64 73
65Some ports allow you to register C<rcv> handlers that can match specific 74Ports allow you to register C<rcv> handlers that can match all or just
66messages. All C<rcv> handlers will receive messages they match, messages 75some messages. Messages will not be queued.
67will not be queued.
68 76
69=item port id - C<noderef#portname> 77=item port id - C<noderef#portname>
70 78
71A port id is normaly the concatenation of a noderef, a hash-mark (C<#>) as 79A port ID is the concatenation of a noderef, a hash-mark (C<#>) as
72separator, and a port name (a printable string of unspecified format). An 80separator, and a port name (a printable string of unspecified format). An
73exception is the the node port, whose ID is identical to its node 81exception is the the node port, whose ID is identical to its node
74reference. 82reference.
75 83
76=item node 84=item node
77 85
78A node is a single process containing at least one port - the node 86A node is a single process containing at least one port - the node port,
79port. You can send messages to node ports to find existing ports or to 87which provides nodes to manage each other remotely, and to create new
80create new ports, among other things. 88ports.
81 89
82Nodes are either private (single-process only), slaves (connected to a 90Nodes are either private (single-process only), slaves (connected to a
83master node only) or public nodes (connectable from unrelated nodes). 91master node only) or public nodes (connectable from unrelated nodes).
84 92
85=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id> 93=item noderef - C<host:port,host:port...>, C<id@noderef>, C<id>
134 kil $SELF, die => $msg; 142 kil $SELF, die => $msg;
135} 143}
136 144
137=item $thisnode = NODE / $NODE 145=item $thisnode = NODE / $NODE
138 146
139The C<NODE> function returns, and the C<$NODE> variable contains 147The C<NODE> function returns, and the C<$NODE> variable contains the
140the noderef of the local node. The value is initialised by a call 148noderef of the local node. The value is initialised by a call to
141to C<become_public> or C<become_slave>, after which all local port 149C<initialise_node>.
142identifiers become invalid.
143 150
144=item $noderef = node_of $port 151=item $noderef = node_of $port
145 152
146Extracts and returns the noderef from a portid or a noderef. 153Extracts and returns the noderef from a port ID or a noderef.
147 154
148=item initialise_node $noderef, $seednode, $seednode... 155=item initialise_node $noderef, $seednode, $seednode...
149 156
150=item initialise_node "slave/", $master, $master... 157=item initialise_node "slave/", $master, $master...
151 158
154it should know the noderefs of some other nodes in the network. 161it should know the noderefs of some other nodes in the network.
155 162
156This function initialises a node - it must be called exactly once (or 163This function initialises a node - it must be called exactly once (or
157never) before calling other AnyEvent::MP functions. 164never) before calling other AnyEvent::MP functions.
158 165
159All arguments are noderefs, which can be either resolved or unresolved. 166All arguments (optionally except for the first) are noderefs, which can be
167either resolved or unresolved.
168
169The first argument will be looked up in the configuration database first
170(if it is C<undef> then the current nodename will be used instead) to find
171the relevant configuration profile (see L<aemp>). If none is found then
172the default configuration is used. The configuration supplies additional
173seed/master nodes and can override the actual noderef.
160 174
161There are two types of networked nodes, public nodes and slave nodes: 175There are two types of networked nodes, public nodes and slave nodes:
162 176
163=over 4 177=over 4
164 178
165=item public nodes 179=item public nodes
166 180
167For public nodes, C<$noderef> must either be a (possibly unresolved) 181For public nodes, C<$noderef> (supplied either directly to
168noderef, in which case it will be resolved, or C<undef> (or missing), in 182C<initialise_node> or indirectly via a profile or the nodename) must be a
169which case the noderef will be guessed. 183noderef (possibly unresolved, in which case it will be resolved).
170 184
171Afterwards, the node will bind itself on all endpoints and try to connect 185After resolving, the node will bind itself on all endpoints and try to
172to all additional C<$seednodes> that are specified. Seednodes are optional 186connect to all additional C<$seednodes> that are specified. Seednodes are
173and can be used to quickly bootstrap the node into an existing network. 187optional and can be used to quickly bootstrap the node into an existing
188network.
174 189
175=item slave nodes 190=item slave nodes
176 191
177When the C<$noderef> is the special string C<slave/>, then the node will 192When the C<$noderef> (either as given or overriden by the config file)
193is the special string C<slave/>, then the node will become a slave
178become a slave node. Slave nodes cannot be contacted from outside and will 194node. Slave nodes cannot be contacted from outside and will route most of
179route most of their traffic to the master node that they attach to. 195their traffic to the master node that they attach to.
180 196
181At least one additional noderef is required: The node will try to connect 197At least one additional noderef is required (either by specifying it
182to all of them and will become a slave attached to the first node it can 198directly or because it is part of the configuration profile): The node
183successfully connect to. 199will try to connect to all of them and will become a slave attached to the
200first node it can successfully connect to.
184 201
185=back 202=back
186 203
187This function will block until all nodes have been resolved and, for slave 204This function will block until all nodes have been resolved and, for slave
188nodes, until it has successfully established a connection to a master 205nodes, until it has successfully established a connection to a master
189server. 206server.
190 207
191Example: become a public node listening on the default node. 208Example: become a public node listening on the guessed noderef, or the one
209specified via C<aemp> for the current node. This should be the most common
210form of invocation for "daemon"-type nodes.
192 211
193 initialise_node; 212 initialise_node;
213
214Example: become a slave node to any of the the seednodes specified via
215C<aemp>. This form is often used for commandline clients.
216
217 initialise_node "slave/";
218
219Example: become a slave node to any of the specified master servers. This
220form is also often used for commandline clients.
221
222 initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
194 223
195Example: become a public node, and try to contact some well-known master 224Example: become a public node, and try to contact some well-known master
196servers to become part of the network. 225servers to become part of the network.
197 226
198 initialise_node undef, "master1", "master2"; 227 initialise_node undef, "master1", "master2";
201 230
202 initialise_node 4041; 231 initialise_node 4041;
203 232
204Example: become a public node, only visible on localhost port 4044. 233Example: become a public node, only visible on localhost port 4044.
205 234
206 initialise_node "locahost:4044"; 235 initialise_node "localhost:4044";
207
208Example: become a slave node to any of the specified master servers.
209
210 initialise_node "slave/", "master1", "192.168.13.17", "mp.example.net";
211 236
212=item $cv = resolve_node $noderef 237=item $cv = resolve_node $noderef
213 238
214Takes an unresolved node reference that may contain hostnames and 239Takes an unresolved node reference that may contain hostnames and
215abbreviated IDs, resolves all of them and returns a resolved node 240abbreviated IDs, resolves all of them and returns a resolved node
252=item snd $port, type => @data 277=item snd $port, type => @data
253 278
254=item snd $port, @msg 279=item snd $port, @msg
255 280
256Send the given message to the given port ID, which can identify either 281Send the given message to the given port ID, which can identify either
257a local or a remote port, and can be either a string or soemthignt hat 282a local or a remote port, and must be a port ID.
258stringifies a sa port ID (such as a port object :).
259 283
260While the message can be about anything, it is highly recommended to use a 284While the message can be about anything, it is highly recommended to use a
261string as first element (a portid, or some word that indicates a request 285string as first element (a port ID, or some word that indicates a request
262type etc.). 286type etc.).
263 287
264The message data effectively becomes read-only after a call to this 288The message data effectively becomes read-only after a call to this
265function: modifying any argument is not allowed and can cause many 289function: modifying any argument is not allowed and can cause many
266problems. 290problems.
271that Storable can serialise and deserialise is allowed, and for the local 295that Storable can serialise and deserialise is allowed, and for the local
272node, anything can be passed. 296node, anything can be passed.
273 297
274=item $local_port = port 298=item $local_port = port
275 299
276Create a new local port object that can be used either as a pattern 300Create a new local port object and returns its port ID. Initially it has
277matching port ("full port") or a single-callback port ("miniport"), 301no callbacks set and will throw an error when it receives messages.
278depending on how C<rcv> callbacks are bound to the object.
279 302
280=item $port = port { my @msg = @_; $finished } 303=item $local_port = port { my @msg = @_ }
281 304
282Creates a "miniport", that is, a very lightweight port without any pattern 305Creates a new local port, and returns its ID. Semantically the same as
283matching behind it, and returns its ID. Semantically the same as creating
284a port and calling C<rcv $port, $callback> on it. 306creating a port and calling C<rcv $port, $callback> on it.
285 307
286The block will be called for every message received on the port. When the 308The block will be called for every message received on the port, with the
287callback returns a true value its job is considered "done" and the port 309global variable C<$SELF> set to the port ID. Runtime errors will cause the
288will be destroyed. Otherwise it will stay alive. 310port to be C<kil>ed. The message will be passed as-is, no extra argument
311(i.e. no port ID) will be passed to the callback.
289 312
290The message will be passed as-is, no extra argument (i.e. no port id) will 313If you want to stop/destroy the port, simply C<kil> it:
291be passed to the callback.
292 314
293If you need the local port id in the callback, this works nicely: 315 my $port = port {
294 316 my @msg = @_;
295 my $port; $port = port { 317 ...
296 snd $otherport, reply => $port; 318 kil $SELF;
297 }; 319 };
298 320
299=cut 321=cut
300 322
301sub rcv($@); 323sub rcv($@);
324
325sub _kilme {
326 die "received message on port without callback";
327}
302 328
303sub port(;&) { 329sub port(;&) {
304 my $id = "$UNIQ." . $ID++; 330 my $id = "$UNIQ." . $ID++;
305 my $port = "$NODE#$id"; 331 my $port = "$NODE#$id";
306 332
307 if (@_) { 333 rcv $port, shift || \&_kilme;
308 rcv $port, shift;
309 } else {
310 $PORT{$id} = sub { }; # nop
311 }
312 334
313 $port 335 $port
314} 336}
315 337
316=item reg $port, $name
317
318=item reg $name
319
320Registers the given port (or C<$SELF><<< if missing) under the name
321C<$name>. If the name already exists it is replaced.
322
323A port can only be registered under one well known name.
324
325A port automatically becomes unregistered when it is killed.
326
327=cut
328
329sub reg(@) {
330 my $port = @_ > 1 ? shift : $SELF || Carp::croak 'reg: called with one argument only, but $SELF not set,';
331
332 $REG{$_[0]} = $port;
333}
334
335=item rcv $port, $callback->(@msg) 338=item rcv $local_port, $callback->(@msg)
336 339
337Replaces the callback on the specified miniport (after converting it to 340Replaces the default callback on the specified port. There is no way to
338one if required). 341remove the default callback: use C<sub { }> to disable it, or better
339 342C<kil> the port when it is no longer needed.
340=item rcv $port, tagstring => $callback->(@msg), ...
341
342=item rcv $port, $smartmatch => $callback->(@msg), ...
343
344=item rcv $port, [$smartmatch...] => $callback->(@msg), ...
345
346Register callbacks to be called on matching messages on the given full
347port (after converting it to one if required) and return the port.
348
349The callback has to return a true value when its work is done, after
350which is will be removed, or a false value in which case it will stay
351registered.
352 343
353The global C<$SELF> (exported by this module) contains C<$port> while 344The global C<$SELF> (exported by this module) contains C<$port> while
354executing the callback. 345executing the callback. Runtime errors during callback execution will
346result in the port being C<kil>ed.
355 347
356Runtime errors during callback execution will result in the port being 348The default callback received all messages not matched by a more specific
357C<kil>ed. 349C<tag> match.
358 350
359If the match is an array reference, then it will be matched against the 351=item rcv $local_port, tag => $callback->(@msg_without_tag), ...
360first elements of the message, otherwise only the first element is being
361matched.
362 352
363Any element in the match that is specified as C<_any_> (a function 353Register callbacks to be called on messages starting with the given tag on
364exported by this module) matches any single element of the message. 354the given port (and return the port), or unregister it (when C<$callback>
355is C<$undef>).
365 356
366While not required, it is highly recommended that the first matching 357The original message will be passed to the callback, after the first
367element is a string identifying the message. The one-string-only match is 358element (the tag) has been removed. The callback will use the same
368also the most efficient match (by far). 359environment as the default callback (see above).
369 360
370Example: create a port and bind receivers on it in one go. 361Example: create a port and bind receivers on it in one go.
371 362
372 my $port = rcv port, 363 my $port = rcv port,
373 msg1 => sub { ...; 0 }, 364 msg1 => sub { ... },
374 msg2 => sub { ...; 0 }, 365 msg2 => sub { ... },
375 ; 366 ;
376 367
377Example: create a port, bind receivers and send it in a message elsewhere 368Example: create a port, bind receivers and send it in a message elsewhere
378in one go: 369in one go:
379 370
380 snd $otherport, reply => 371 snd $otherport, reply =>
381 rcv port, 372 rcv port,
382 msg1 => sub { ...; 0 }, 373 msg1 => sub { ... },
383 ... 374 ...
384 ; 375 ;
385 376
386=cut 377=cut
387 378
390 my ($noderef, $portid) = split /#/, $port, 2; 381 my ($noderef, $portid) = split /#/, $port, 2;
391 382
392 ($NODE{$noderef} || add_node $noderef) == $NODE{""} 383 ($NODE{$noderef} || add_node $noderef) == $NODE{""}
393 or Carp::croak "$port: rcv can only be called on local ports, caught"; 384 or Carp::croak "$port: rcv can only be called on local ports, caught";
394 385
395 if (@_ == 1) { 386 while (@_) {
387 if (ref $_[0]) {
388 if (my $self = $PORT_DATA{$portid}) {
389 "AnyEvent::MP::Port" eq ref $self
390 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
391
392 $self->[2] = shift;
393 } else {
396 my $cb = shift; 394 my $cb = shift;
397 delete $PORT_DATA{$portid};
398 $PORT{$portid} = sub { 395 $PORT{$portid} = sub {
399 local $SELF = $port; 396 local $SELF = $port;
400 eval { 397 eval { &$cb }; _self_die if $@;
401 &$cb 398 };
402 and kil $port;
403 }; 399 }
404 _self_die if $@; 400 } elsif (defined $_[0]) {
405 };
406 } else {
407 my $self = $PORT_DATA{$portid} ||= do { 401 my $self = $PORT_DATA{$portid} ||= do {
408 my $self = bless { 402 my $self = bless [$PORT{$port} || sub { }, { }, $port], "AnyEvent::MP::Port";
409 id => $port,
410 }, "AnyEvent::MP::Port";
411 403
412 $PORT{$portid} = sub { 404 $PORT{$portid} = sub {
413 local $SELF = $port; 405 local $SELF = $port;
414 406
415 eval {
416 for (@{ $self->{rc0}{$_[0]} }) { 407 if (my $cb = $self->[1]{$_[0]}) {
417 $_ && &{$_->[0]} 408 shift;
418 && undef $_; 409 eval { &$cb }; _self_die if $@;
419 } 410 } else {
420
421 for (@{ $self->{rcv}{$_[0]} }) {
422 $_ && [@_[1 .. @{$_->[1]}]] ~~ $_->[1]
423 && &{$_->[0]} 411 &{ $self->[0] };
424 && undef $_;
425 }
426
427 for (@{ $self->{any} }) {
428 $_ && [@_[0 .. $#{$_->[1]}]] ~~ $_->[1]
429 && &{$_->[0]}
430 && undef $_;
431 } 412 }
432 }; 413 };
433 _self_die if $@; 414
415 $self
434 }; 416 };
435 417
436 $self
437 };
438
439 "AnyEvent::MP::Port" eq ref $self 418 "AnyEvent::MP::Port" eq ref $self
440 or Carp::croak "$port: rcv can only be called on message matching ports, caught"; 419 or Carp::croak "$port: rcv can only be called on message matching ports, caught";
441 420
442 while (@_) {
443 my ($match, $cb) = splice @_, 0, 2; 421 my ($tag, $cb) = splice @_, 0, 2;
444 422
445 if (!ref $match) { 423 if (defined $cb) {
446 push @{ $self->{rc0}{$match} }, [$cb]; 424 $self->[1]{$tag} = $cb;
447 } elsif (("ARRAY" eq ref $match && !ref $match->[0])) {
448 my ($type, @match) = @$match;
449 @match
450 ? push @{ $self->{rcv}{$match->[0]} }, [$cb, \@match]
451 : push @{ $self->{rc0}{$match->[0]} }, [$cb];
452 } else { 425 } else {
453 push @{ $self->{any} }, [$cb, $match]; 426 delete $self->[1]{$tag};
454 } 427 }
455 } 428 }
456 } 429 }
457 430
458 $port 431 $port
762convenience functionality. 735convenience functionality.
763 736
764This means that AEMP requires a less tightly controlled environment at the 737This means that AEMP requires a less tightly controlled environment at the
765cost of longer node references and a slightly higher management overhead. 738cost of longer node references and a slightly higher management overhead.
766 739
740=item Erlang has a "remote ports are like local ports" philosophy, AEMP
741uses "local ports are like remote ports".
742
743The failure modes for local ports are quite different (runtime errors
744only) then for remote ports - when a local port dies, you I<know> it dies,
745when a connection to another node dies, you know nothing about the other
746port.
747
748Erlang pretends remote ports are as reliable as local ports, even when
749they are not.
750
751AEMP encourages a "treat remote ports differently" philosophy, with local
752ports being the special case/exception, where transport errors cannot
753occur.
754
767=item * Erlang uses processes and a mailbox, AEMP does not queue. 755=item * Erlang uses processes and a mailbox, AEMP does not queue.
768 756
769Erlang uses processes that selctively receive messages, and therefore 757Erlang uses processes that selectively receive messages, and therefore
770needs a queue. AEMP is event based, queuing messages would serve no useful 758needs a queue. AEMP is event based, queuing messages would serve no
771purpose. 759useful purpose. For the same reason the pattern-matching abilities of
760AnyEvent::MP are more limited, as there is little need to be able to
761filter messages without dequeing them.
772 762
773(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP). 763(But see L<Coro::MP> for a more Erlang-like process model on top of AEMP).
774 764
775=item * Erlang sends are synchronous, AEMP sends are asynchronous. 765=item * Erlang sends are synchronous, AEMP sends are asynchronous.
776 766
777Sending messages in Erlang is synchronous and blocks the process. AEMP 767Sending messages in Erlang is synchronous and blocks the process (and
778sends are immediate, connection establishment is handled in the 768so does not need a queue that can overflow). AEMP sends are immediate,
779background. 769connection establishment is handled in the background.
780 770
781=item * Erlang can silently lose messages, AEMP cannot. 771=item * Erlang suffers from silent message loss, AEMP does not.
782 772
783Erlang makes few guarantees on messages delivery - messages can get lost 773Erlang makes few guarantees on messages delivery - messages can get lost
784without any of the processes realising it (i.e. you send messages a, b, 774without any of the processes realising it (i.e. you send messages a, b,
785and c, and the other side only receives messages a and c). 775and c, and the other side only receives messages a and c).
786 776
798eventually be killed - it cannot happen that a node detects a port as dead 788eventually be killed - it cannot happen that a node detects a port as dead
799and then later sends messages to it, finding it is still alive. 789and then later sends messages to it, finding it is still alive.
800 790
801=item * Erlang can send messages to the wrong port, AEMP does not. 791=item * Erlang can send messages to the wrong port, AEMP does not.
802 792
803In Erlang it is quite possible that a node that restarts reuses a process 793In Erlang it is quite likely that a node that restarts reuses a process ID
804ID known to other nodes for a completely different process, causing 794known to other nodes for a completely different process, causing messages
805messages destined for that process to end up in an unrelated process. 795destined for that process to end up in an unrelated process.
806 796
807AEMP never reuses port IDs, so old messages or old port IDs floating 797AEMP never reuses port IDs, so old messages or old port IDs floating
808around in the network will not be sent to an unrelated port. 798around in the network will not be sent to an unrelated port.
809 799
810=item * Erlang uses unprotected connections, AEMP uses secure 800=item * Erlang uses unprotected connections, AEMP uses secure
846This also saves round-trips and avoids sending messages to the wrong port 836This also saves round-trips and avoids sending messages to the wrong port
847(hard to do in Erlang). 837(hard to do in Erlang).
848 838
849=back 839=back
850 840
841=head1 RATIONALE
842
843=over 4
844
845=item Why strings for ports and noderefs, why not objects?
846
847We considered "objects", but found that the actual number of methods
848thatc an be called are very low. Since port IDs and noderefs travel over
849the network frequently, the serialising/deserialising would add lots of
850overhead, as well as having to keep a proxy object.
851
852Strings can easily be printed, easily serialised etc. and need no special
853procedures to be "valid".
854
855And a a miniport consists of a single closure stored in a global hash - it
856can't become much cheaper.
857
858=item Why favour JSON, why not real serialising format such as Storable?
859
860In fact, any AnyEvent::MP node will happily accept Storable as framing
861format, but currently there is no way to make a node use Storable by
862default.
863
864The default framing protocol is JSON because a) JSON::XS is many times
865faster for small messages and b) most importantly, after years of
866experience we found that object serialisation is causing more problems
867than it gains: Just like function calls, objects simply do not travel
868easily over the network, mostly because they will always be a copy, so you
869always have to re-think your design.
870
871Keeping your messages simple, concentrating on data structures rather than
872objects, will keep your messages clean, tidy and efficient.
873
874=back
875
851=head1 SEE ALSO 876=head1 SEE ALSO
852 877
853L<AnyEvent>. 878L<AnyEvent>.
854 879
855=head1 AUTHOR 880=head1 AUTHOR

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines