[JDEV] Is this a plausible scenario?
Scott Robinson
quad at jabber.org
Thu Dec 2 21:59:11 CST 1999
Interleaved response.
Scott.
* James Husum translated into ASCII [Thu, Dec 02, 1999 at 09:29:33PM -0600][<1.5.4.32.19991203032933.00739aa0 at pop.biznizweb.com>]
[snap]
> If I understand the goals of Jabber, this information (or perhaps a
> notification of a new available bid) could be sent to WAP devices, pagers,
> etc. as well.
>
As of current, we do not have a WAP client nor a SMS transport. See below
for more.
> Is this a plausible scenario? Would Jabber be able to handle something like
> this now? If not, how long might it be before Jabber could handle something
> like this?
>
This is a very realistic scenario, and exactly of the type we envisioned in
the use of XML. A transport/client connected at your database could push the
information/notifications to Jabber clients at any address. (and even to
current oldstyle clients, through transport translation layers) Jabber
clients could also pull information from your database using a similar set
of XML fragments.
The Internet side, Jabber can support right now. The previously mentioned
Wireless side is currently being discussed/designed/developed, though is
simple enough that a working transport could be running within weeks.
> Thanks.
>
> James Husum
> BiznizWEB, Inc.
> http://www.biznizweb.com/
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>
--
quad at jabber.org - Universal ID (www.jabber.org)
http://dsn.itgo.com/ - Homepage
robhome.dhis.org - Home Firewall
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT dpu s+: a--- C++ UL++++ P+ L+++ E- W+ N+ o+ K++ w++
O M V PS+ PE Y+ PGP++ t++ 5++ X+ R tv b++++ DI++++ D++
G+ e+ h! r-- y-
------END GEEK CODE BLOCK------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/19991202/6860737a/attachment-0002.pgp>
More information about the JDev
mailing list