Help-Site Computer Manuals
Software
Hardware
Programming
Networking
  Algorithms & Data Structures   Programming Languages   Revision Control
  Protocols
  Cameras   Computers   Displays   Keyboards & Mice   Motherboards   Networking   Printers & Scanners   Storage
  Windows   Linux & Unix   Mac

Jabber::Component::Proxy
A simple proxy for Jabber Components

Jabber::Component::Proxy - A simple proxy for Jabber Components


NAME

Jabber::Component::Proxy - A simple proxy for Jabber Components


SYNOPSIS


  use Jabber::Component::Proxy

  # Create proxy

  my $proxy = new Jabber::Component::Proxy(

    server    => 'localhost:6789',

    identauth => 'conference.qmacro.dyndns.org',

    realcomp  => 'conference.internal',

    rulefile  => './access.xml',

  );

  $proxy->start;


DESCRIPTION

Jabber::Component::Proxy is a simple proxy mechanism that you can use to control access to your Jabber services. If you attach a component to your Jabber server, and give that component a 'real' resolvable FQDN, people on other Jabber servers can access that component.

This might be what you want. But what if you want to allow access to some people but not others? How can you control access on a domain name basis, for example? Currently component access is all or nothing:

- give a component a resolvable name and the world can use it - give a component an internal name and no one but those connected the same Jabber server as the component can use it

(This is assuming of course you're running an s2s service).

You can effect a sort of access control, for non-local users, using this module.


VERSION

0.01 (early)


AUTHOR

DJ Adams


SEE ALSO

Jabber::Connection

Programminig
Wy
Wy
yW
Wy
Programming
Wy
Wy
Wy
Wy