3 More Discussions You Might Find Interesting
1. What is on Your Mind?
Greetings friends, I was looking for something about <i>Lua Script Language<i/> and I didn'y find anything, and then I had a thought that It'd be easy if in the Programming Topic there are subtopics with is organized by programming languages.
Just a thought (0 Replies)
Discussion started by: pharaoh
0 Replies
2. UNIX for Advanced & Expert Users
Would like to confirm the ff. I got confused actually with the version I needed to download that will work on glassfish 3.0.1
a. Debian Squeeze (HP DL360). Need to use java version6
On Debian, I did apt-get install sun-java6-jdk. So when I check it's
java version "1.6.0_22"
Java(TM) SE... (1 Reply)
Discussion started by: lhareigh890
1 Replies
3. Post Here to Contact Site Administrators and Moderators
No wonder that so few topics are closed. Looking for the fourth time as I do not find! (4 Replies)
Discussion started by: popescu1954
4 Replies
LEARN ABOUT DEBIAN
tm::objectable
TM::ObjectAble(3pm) User Contributed Perl Documentation TM::ObjectAble(3pm)
NAME
TM::Synchronizable - Topic Maps, trait for storing objects into backends
SYNOPSIS
my $tm = .... # get a topic map from somewhere
use Class::Trait;
Class::Trait->apply ($tm, "TM::ObjectAble");
my %store; # find yourself a proper store, can be anything HASHish
# append it to the list of stores, or ....
push @{ $tm->storages }, \%store;
# prepend it to the list of stores
unshift @{ $tm->storages }, \%store;
# store it (the proper storage will take it)
$tm->objectify ('tm:some-topic', "whatever object or data");
# get it back
my @objects = $tm->object ('tm:some-topic', 'tm:some-topic2');
# get rid of it
$tm->deobjectify ('tm:some-topic');
DESCRIPTION
This trait implements functionality to store arbitrary data on a per-topic basis.
Conceptually, the storage can be thought as one large hash, as keys being use the internal topic identifiers, as values the object data.
But to allow different topics to store their object data in different places, this interface works with a list of such hashes. Each hash
(native or tied to some implementation) in the list is visited (starting from the start of the list) and can take over the storage. Whether
this is based on the topic id, on some other topic information, or on the MIME type of the data (if it has one), is up to the
implementation to decide.
INTERFACE
Methods
storages
$listref = $tm->storages
This method returns an array reference. You can "unshift" or "push" your storage implementation onto this list.
Example:
my %store1;
push @{ $tm->storages }, \%store1
objectify
$tm->objectify ($tid => $some_data, ...);
This method stores actually the data. It takes a hash, with the topic id as keys and according values and tries to find for each of the
pairs an appropriate storage. If none can be found, it will raise an exception.
NOTE: Yes, this is a stupid name.
deobjectify
$tm->deobjectify ($tid, ...)
This method removes any data stored for the provided topic(s). If no data can be found in the appropriate storage, an exception will be
raised.
object
@objects = $tm->object ($tid, ...)
This method returns any data stored for the provided objects. If no data can be found for a particular topic, then "undef" will be
returned.
SEE ALSO
TM
AUTHOR INFORMATION
Copyright 20(10), Robert Barta <drrho@cpan.org>, All rights reserved.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
http://www.perl.com/perl/misc/Artistic.html
perl v5.10.1 2010-10-27 TM::ObjectAble(3pm)
06-05-2004
