[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jabber-jdev
Subject:    Re: [jdev] RE: jdev Digest, Vol 16, Issue 30
From:       "Shuaib Karim" <skarim () ifs ! tuwien ! ac ! at>
Date:       2005-05-31 7:36:02
Message-ID: 000601c565b3$6550e980$dda8a8c0 () ifsb92fe1fe558
[Download RAW message or body]

Hi Brijesh Singh,
Thanks for your comprehensive reply. Now it seems, Jabber would do the job i 
need in our project.

Regards,

Shuaib
----- Original Message ----- 
From: "Brijesh" <brijesh@india.hp.com>
To: <jdev@jabber.org>
Sent: Tuesday, May 31, 2005 6:24 AM
Subject: [jdev] RE: jdev Digest, Vol 16, Issue 30


> Hi Shuaib,
>
> It looks like you need a asynchronous message router where different
> entities(user, apps, devices) get connected to this message router to
> exchange messages in async fashion.
>
> Jabber protocol does the same & more precisely you can use J-EAI as 
> message
> bus. Here you can plug-in all your users, devices, apps with J-EAI to
> exchange messages in async fashion.
>
> J-EAI routing algorithms are :
>
> - Point-to-point communication, through the server
> - Direct point-to-point message exchange from client to client
> - Channel-based publish & subscribe mechanism (conforms to JEP-0060)
> - Message pattern-based publish & subscribe mechanism based on XPATH
>
> You can find out more details at
> http://www.erlang-projects.org/Members/mremond/contributions/j-eai_objectweb
> _arc/block_10968872179181/file
>
> & http://www.erlang-projects.org/Public/news/j-eai_open_source_j/view
>
> Regards
>
> Brijesh Singh
>
> -----------------------------------------------------------------
>
>
> Hi Alex,
> Thanks for the response.
> We are building a personal information management system, which will 
> manage
> the user's lifetime information semantically. Our project's name is
> SemanticLIFE. Following is our SW design:
> There are various components , e.g., Data feed (capture and stores the
> diverse range of user's data, e.g., emails, browsed web sessions, 
> processes
> running on his machine, and any file he want to upload such as photos,
> movies, .doc, .jpeg etc. etc.), analysis engine (analysing the stored
> entities in previous step and finding semantic relations between the
> information. Now the dumb information captured in first step will be 
> stored
> again semantically, i.e., as ontologies), Query, Storage and some others,
> besides the main component MessageHandler which is the entry point of our
> core machine. Every module sends the data as an XML message to the Message
> Handler which then routes it to the appropriate component by looking at 
> some
> header field, after adding time stamp and a unique message id.
> By asynchronous messaging, what i mean is that the sender componet should
> not get blocked after sending a message for waiting its response, which
> might take some time. Consider two components c1, c2 communicating via
> message handler. c1 sends message to c2, and forgets about the response.
> After certain time, when c2 accomplishes his job for c1's message, it send
> the response message (original request message from c1 is also 
> encapsulated
> within) to c1 via message handler. Now c1 should retrieve that message 
> from
> its queue and process it.
> There are some other solutions too for accomplishing this architecture 
> such
> as jms publish-subscribe, jade agent development framework etc. But we are
> searching a lightweight and efficient solution.
>
>
> Sorry for the lengthy mail!
>
> With thanks and best regards,
>
> Shuaib
>
>
>
>  _____
>
> << ella for Spam Control >> has removed 2093 Spam messages and set aside 
> 740
> Newsletters for me
> You can use it too - and it's FREE!  www.ellaforspam.com
>
>
> _______________________________________________
> jdev mailing list
> jdev@jabber.org
> http://mail.jabber.org/mailman/listinfo/jdev
> 

_______________________________________________
jdev mailing list
jdev@jabber.org
http://mail.jabber.org/mailman/listinfo/jdev
[prev in list] [next in list] [prev in thread] [next in thread]