Providing a registered service

If you want to let users register your email, address book, or To Do service in the Service Registry, display a card that lets the user request the following URL:

device:home/register?svc=svc&url=url&name=name

For example, suppose you want users to be able to register your service as an address book and your service has the following URL:

http://myaddr.foo.com/addrbook.cgi

You could use a WML deck similar to the following to register it:

<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//PHONE.COM//DTD WML 1.1//EN"
"http://www.phone.com/dtd/wml11.dtd" >
<!-- Add Registered Service -->
<wml>
    <card title="AddRegSvc">
      <do type="accept" label="Yes">
          <spawn onexit="#AddDone" href="device:home/register?
           svc=AddrBook&amp;url=
            http://myaddr.foo.com/addrbook.cgi&amp;name=
            MyAddr">
         </spawn>
       </do>
      <p>
         Register MyAddr as your address book?
      </p>
    </card>
<card title="AddDone" id="AddDone">
      <p>
         MyaAddr registered.
      </p>
</card>
</wml>

Figure  7-6.     the user to register a service

To properly implement a registered service, it must support the minimum functionality and interface for its service category (described on page 112 for email services, page 113 for address book services, and page 118 for To Do services).

---

Security issues for registered services

In addition to supporting the functionality and interface described in the sections above, registered services should observe security precautions to protect users and themselves. You should use the following guidelines when you implement a service that users can register:

• A registered email service should display any message another service has asked it to send, allowing the user to confirm it. This ensures that a malicious service cannot send a message without the user's knowledge.
• A registered address book service should display any address entry it is about to add at the request of another service.
• For secure information, the service should employ username-password and certificate authentication.