RE: [Radioactive-developers] RE: Status

[Felipe N. <fel...@in...>]

Hi Somen,

That helped, yes.=20

My dissertation is changing a little as I see too little has been done =
on
lower level issues. So, if I wanted to track and trace medications along =
the
supply chain, now I see I need to first track and trace products inside =
"my
own organization". So that means doing what you said: having n =
distributed
middlewares with m readers each one, tracking EPCs along the =
organization,
talking to each other (some Multi-Agent Systems characteristics). I'll
definitely do something about this. Maybe in the near future I can help =
you
guys whit some things I'll have done...

For the data being transferred in an XML format, is there a definition =
on
that dtd? If PML no longer exist, is there aynthing substituting it, I =
mean
is EPCglobal leading this also, or will be no standards on this issue?

Tks again
Felipe


-----Original Message-----
From: Somen Mondal [mailto:som...@ra...]=20
Sent: s=E1bado, 2 de outubro de 2004 18:29
To: 'Felipe Nascimento'; rad...@li...
Subject: RE: [Radioactive-developers] RE: Status

Hi Felipe,

When you say delete EPC, you can never really delete an epc.  Perhaps =
you
meant left the range of a reader?  I agree with you, the middleware does
raise events and clients can subscribe to these events (ALE).  I =
middleware
can be configured to raise any kind of events that we see fit.  There is =
no
specification, so its up to us. =20

The middleware should keep track of all the readers connected to it.  =
The
middleware will keep track of all the events across all the readers, so =
if
one reader detects an epc and then "deletes" it, the middleware will =
sense
when the next reader gets the epc signal and keep track of it.

I think your assuming that that relationship of reader to middleware =
will be
one to one.  There can be many readers for one middleware instance.  =
Right
now, we are dealing with one instance of the middleware, but, in the =
future
we could have multiple instances of the middleware where we would either
have to have some sort of distributed system and have all the middleware
instances talk to each other OR have it done at the higher levels.  We =
could
basically have a client subscribe to each middleware instance =
individually.
But this is something for down the road.  Shaun and I had discussed a
distributed style middleware based on nodes where all clients would only
ever talk to a super node.  This is a definite possibility.  =20

All communication for now will use JMS and http(web services)..  For =
data,
we'll always use an XML format.  PML no longer exists really, but =
something
similar.

Hope that helps,
Somen

-----Original Message-----
From: rad...@li...
[mailto:rad...@li...] On Behalf Of
Felipe Nascimento
Sent: Friday, October 01, 2004 5:37 PM
To: rad...@li...
Subject: RE: [Radioactive-developers] RE: Status

Hi guys,

the middleware receive reads from a reader (or more than one) and can =
raise
events, right? The most low level events I can think of are:
a) added EPC;
b) deleted EPC (when an epc was there and is not anymore)

Will the middleware raise deletion events? If yes, will the middleware =
treat
cases when an EPC was deleted from one reader and added to another? Or =
this
is a higher level application responsibility?

What are your thoughts about these raising events? Will different =
instances
of middleware talk to each other, maybe to detect an EPC has moved? Or =
again
this is a higher level app responsibility?

How will events be raised, in terms of message format and protocol? PML =
and
SOAP? JMS?

This is important for me so I can visualize if I need to develop those
deletion, movement, etc, functionalities in my application, or I should
contribute to RadioActive, maybe in this ALE module (I believe these =
would
be ALE's funcionalities).

Tks
Felipe

________________________________

From: rad...@li...
[mailto:rad...@li...] On Behalf Of
Somen Mondal
Sent: quinta-feira, 30 de setembro de 2004 23:13
To: rad...@li...;
rad...@li...
Subject: [Radioactive-developers] RE: Status



Hi Guys,

=20

Just wanted to give you the status of our project.

=20

We are currently developing 3 pieces of software:

=20

1)       the EPC-IS prototype

2)       the middleware

3)       a hardware simulator

=20

Randy is heading up the hardware simulator, and our goal is to have a =
driver
interface to simulate different readers and to generate the reader's =
network
traffic.  Shaun, Pawel and I are developing the base EPC-IS and =
middleware.
Once we have the base, it will be easier for more people to help develop =
the
rest. =20

=20

I really think our prototype software is going to get pretty complicated =
and
can probably be a release 0.1.=20

=20

Thanks,

Somen




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal =
Use
IT products in your business? Tell us what you think of them. Give us =
Your
Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Radioactive-developers mailing list
Rad...@li...
https://lists.sourceforge.net/lists/listinfo/radioactive-developers