[mactel]

.
About creating a advertisment within the TelProxy:

Example of a ad:

Plumber
24 Hour Fast Response Plumbers
10% Book Online Discount Today!
(your website link)


Some Explanations:

1.) Dot Tel DNS records consist out of three types: LOC, NAPTR and TXT.

2.) DNS TXT records have a records suffix, named ".tad".

3.) ".tad" has to be stored in a special sub-folder within the .tel domain.

4.) I guess, that the subfolder would be named: "my.tel.tad".

5.) The ".tad" folder contains records, such as the title, label, description, and URI to use in the advertisement, as well as display settings which enable the domain owner to position the advert in their chosen place on the page (top, bottom, or right) when the content is delivered to the proxy page.

Example of DNS TXT ".tad" records, that have to be sotred in the ".tad" sub folder
(often described as "_ad folder", so I guess, our folder could be named "plumber_ad" folder (within: "my.tel.tad"?)
- It may be just ok, to store the records in the "plumber_ad" folder?
However, here is what the records look like, for the "Plumber" advertisment:

IN TXT ".tad" "1" "1" "51"
"Plumber"
"www.ReactFast.co.uk/Plumbers"
"uri" "http://www.reactfast.co.uk" "uri" "=243423543&z=42342343"
"desc" "24 Hour Fast Response Plumbers" "desc" "10% Book Online Discount Today !"

6.) When a Proxy page loads a .tel domain, it checks/veryfies the format and the settings of the advert contents, and then makes them visible.

Example?:
I guess, that these settings, are the advert settings:

????: NamePros.com http://www.namepros.com/domain-name-discussion/561820-the-official-tel-discussion-thread.html
<typ:storeRecordRequest domainName=" stead.te">
<typ:txt profiles="_all_" owner="_ad">
<typ:text>.tad</typ:text>
<typ:text>1</typ:text>
<typ:text>1</typ:text>
<typ:text>100</typ:text>
<typ:text>Title of the ad</typ:text>
<typ:text>lable of the ad</typ:text>
<typ:text>uri</typ:text>
<typ:text>The new way to communicate</typ:text>
<typ:text>desc</typ:text>
<typ:text>sample description</typ:text>
</typ:txt>
</typ:storeRecordRequest>
.



To be continued.
.

[sdsinc]

Originally Posted by mactel

. . There is a problem: ????: NamePros.com http://www.namepros.com/showthread.php?t=561820 1.) Telnic addresses its intructions papers and manuals only to developers. 2.) Not even all developers can follow and understand those guides. 3.) Generally, all such guides appear to be insufficent, uncompleat and confusing.

I thought .tel is so easy your grandma could use it ?

[kukgle]

Great news, now .tel is making money.

[liming]

Originally Posted by kukgle

Great news, now .tel is making money.

Too early!
????: NamePros.com http://www.namepros.com/showthread.php?t=561820
No signs show people check .tel
Click ads is next next step

[mis_chiff]

I have been reading this stuff about the ads...
and I have 2 questions...more - but I'll start with these 2.

Who supplies the ads/feeds?
Who pays us?

[mactel]

Telnic Ltd. provides a Java-based TelHosting Software application. This application interacts with the DNS directly, and exposes a publicly available web service, using SOAP over HTTP as its protocol. Client applications implementing this SOAP interface can work with the TelHosting Software application to perform all .tel-related operations.

All APIs work by receiving request messages from the clients and sending response messages back to them unless the request message requires no response. All messages are expressed in XML, and their respective syntax is specified by an XML schema; see List of Schema Files. The messages must follow the specific format, see Message Format.

In addition to the client service API, the TelHosting Software exposes an internal API for administration purposes. That API is available only to users with specific permissions (TelHosting Providers) and is not covered in this document.

Document about TelHosting SOAP API :
TelHosting Client SOAP API Reference
About this Document:

This document describes the TelHosting SOAP API, which can be used for managing and publishing contact information in .tel domain DNS records.

The reference is targeted at developers interested in creating new .tel client applications and enhancing existing ones. The document assumes that you are familiar with application programming standard SOAP (Simple Object Access Protocol) and that you understand the key concepts of the .tel innovative technology. See Related Links for references to relevant materials.

With this reference, you will learn about:

*The objects used in the interface
????: NamePros.com http://www.namepros.com/showthread.php?t=561820
*The functions available to manipulate all those objects: domains, resource records, and profiles
*Specific usage requirements for each function

-----------------------------------

1,) DNS TXT ".tad" has to be stored in a special sub-folder within the .tel domain.

2.) How do I store DNS TXT ".tad" in my special sub-folder?:
????: NamePros.com http://www.namepros.com/showthread.php?t=561820

Go to:
storeRecord

About storeRecord:

This operation allows a single record to be stored.
storeRecordRequest

Exactly one of the top-level elements with its sub-elements must be present to signify the type of record. Each valid child element of the storeRecordRequest element (listed in the second part of the table below) specifies a DNS record type, and uses all the attributes .

-----------

Element Name:
txt

Description:
One or multiple subelements <text> to specify the free text contact data.

Conclusion:
To specify a TXT advert text data, you must write:
<text>advertext<text>

-------------

Attribute Name:
owner

Description:
Optional Owner name of the record relative to the domain in which it is contained. Similar to the DNS notation, an at-sign (@) denotes the domain’s name itself.

--------------------

Example:

Create a new TXT record with the owner name sample.reggie.tel associated with profile 5:

Request:

<typ:storeRecordRequest domainName="reggie.tel">
<typ:txt ttl="3600" owner="sample" profiles="5" groups="">
<typ:text>Hello World!</typ:text>
</typ:txt>
</typ:storeRecordRequest>

Response:

<storeRecordResponse xmlns="http://xmlns.telnic.org/ws/nsp/client/record/types-1.0">
<id>61</id>
</storeRecordResponse>
.
Your ISP has to provide you with a adaptation / adjustment of the web interface, the so called
"Internal .Tel Adminsistration API". Otherwhise, you are not able to create advertisments within your .tel domain (as a developer).
.

[Steven]

mactel, out of curiosity, do you work for .tel or affiliated with telnic in any way?

[steveteva]

Originally Posted by mis_chiff

I have been reading this stuff about the ads... and I have 2 questions...more - but I'll start with these 2. Who supplies the ads/feeds? Who pays us?

Actually this is insite advertising, meaning that you provide ads and publisher pays you to list their ads, just regular advertising, there are no adsense possibility at this moment as it can't parse live ads from google, it just display what ever you want as fixed text, you can add publisher ads, free ads, affiliate program ads...

[DubDubDubDot]

Originally Posted by mis_chiff

I have been reading this stuff about the ads... ????: NamePros.com http://www.namepros.com/showthread.php?t=561820 and I have 2 questions...more - but I'll start with these 2. Who supplies the ads/feeds? Who pays us?

You have to go get your own advertisers and invoice them.

[mactel]

.
@ Steven:
Your quote:
"mactel, out of curiosity, do you work for .tel or affiliated with telnic in any way?"

Hi there,
No I do not.
I am owner of a big domain portfolion. Including a big amount of .tel domain names.

So I am naturally interesten in:

- Promoting .tel
- Populating .tel domains
- Using all features that Telnic offers, such as the "Contact Us" page, and advertising within the .tel domain

I am Swiss/Britsh, living in Switzerland, working together with my ISP/programmer (Germany), my work partner/generalist (Germany), my webdesigner/programmer (Poland), as well as webmasters in Switzerland and Germany.

I am not only focused at .tel domains:
I take part at all important domain auctions.
And I create, sell, or develope domain names.

Best regards
????: NamePros.com http://www.namepros.com/showthread.php?t=561820

.
P.S.:
All thes .tel domain owners, who have ads on their TelProxy, are ISP's, who have a specific permission from Telnic, as a TelHosting provider, to have and use a internal API for adminstration purposes.

So, that is why, they have got ads in their .tel domain, and we not.

(Remember the bluffer, only showing his .tel domains, full of nice adverts, but not wanting to explain, how to advertise within .tel domains)...
.

[mis_chiff]

Originally Posted by steveteva

Actually this is insite advertising, meaning that you provide ads and publisher pays you to list their ads, just regular advertising, there are no adsense possibility at this moment as it can't parse live ads from google, it just display what ever you want as fixed text, you can add publisher ads, free ads, affiliate program ads...

So I could put my codes from an affiliate related to my .tel on my .tel?
It's an ad that shows just text, but is in an image.
and I get the credit if clicked? (sorry, very confused as to how this works)

Originally Posted by DubDubDubDot

You have to go get your own advertisers and invoice them.

Thanks dubdub
????: NamePros.com http://www.namepros.com/showthread.php?t=561820

I know that'll never happen...

[steveteva]

Originally Posted by mis_chiff

So I could put my codes from an affiliate related to my .tel on my .tel? It's an ad that shows just text, but is in an image. and I get the credit if clicked? (sorry, very confused as to how this works) Thanks dubdub I know that'll never happen...

Yes you put your affiliate link and text you want related to your .tel and you get credit or not depending on what affiliate program you have choosen. Also you can put anything like on tahiti.tel or tans.tel or condos.tel it's up to you. It's not image but coding that is stored in dns.

[mis_chiff]

Thanks for that, they look alright

But not seeing them as affiliate codes - just direct to the websites
or is the affiliate code somehow hidden?

[steveteva]

Originally Posted by mis_chiff

Thanks for that, they look alright ????: NamePros.com http://www.namepros.com/showthread.php?t=561820 But not seeing them as affiliate codes - just direct to the websites or is the affiliate code somehow hidden?

Because none of these .tel owners have linked to affiliate program that's why you see what they link to but you can add what ever link you want (affiliate program, website...)

[mis_chiff]

Originally Posted by steveteva

Because none of these .tel owners have linked to affiliate program that's why you see what they link to but you can add what ever link you want (affiliate program, website...)

Ahhh ok, thanks steveteva for explaining it for me, I think I got it

[kprobe]

Originally Posted by mactel

. ????: NamePros.com http://www.namepros.com/showthread.php?t=561820 @ mactel: Your quote: All thes .tel domain owners, who have ads on their TelProxy, are ISP's, who have a specific permission from Telnic, as a TelHosting provider, to have and use a internal API for adminstration purposes. So, that is why, they have got ads in their .tel domain, and we not. (Remember the bluffer, only showing his .tel domains, full of nice adverts, but not wanting to explain, how to advertise within .tel domains)... .

Don't know where you get all this info, but you are totally incorrect. Every tel owner can place ads on their .tel domains, no ISP nor permission is needed. True you need SOAP API calls, but there are no restriction. I have created my own experimental interface for testing adverts and anyone is free to use it ....
Quick update of your TEL domain header, free text keywords and affiliate advertisements
Many people have already put ads in place with it. Enjoy.
Mark

[mactel]

.
I wrote a email to a ISP in Poland, who is a .tel specialist.

And I asked him, if he could kindly provide me with a "How To" about integrating advertisments within .tel.

He promtly replied to me, with the following information:

1.) Use SOAP with 'storeRecord' for adding TXT ('.tad') with '_ad' as
owner.

2.) The syntax is described in the advertisments.pdf from Telnic.

3.) See also, the documentation for storeRecord (api/client-soap/storerecord.html)
????: NamePros.com http://www.namepros.com/showthread.php?t=561820

4.) Quote: "Also, I can see some apps, which will come soon with options for creating ads. You can check: mytel.me/quick-tel-update.php. (but be careful with important domains - msg "still working out the bugs")."

[kprobe]

Originally Posted by mis_chiff

So I could put my codes from an affiliate related to my .tel on my .tel? ????: NamePros.com http://www.namepros.com/showthread.php?t=561820 It's an ad that shows just text, but is in an image. and I get the credit if clicked? (sorry, very confused as to how this works) Originally Posted by DubDubDubDot View Post You have to go get your own advertisers and invoice them. Thanks dubdub I know that'll never happen...

Join any affiliate program, grab your encoded links (without images) and place as text adverts on your own .tel using a free tool like Quick update of your TEL domain header, free text keywords and affiliate advertisements - no need to invoice - they send you a cheque.
Mark

---------- Post added at 10:58 PM ---------- Previous post was at 10:56 PM ----------

Originally Posted by mis_chiff

Thanks for that, they look alright But not seeing them as affiliate codes - just direct to the websites or is the affiliate code somehow hidden?

I have an affiliate ad here ...
word-games.tel
Mark

[mactel]

.
Ok: Then show me some one, where to store the records, and how to create the '_ad' folder.

I always understand, that one should first store the records, and then create the '_ad' folder.

And then again, I read and understand in the white paper: instead of creating a '_ad' folder, one should use the "owner parameter", with '_ad' as owner.

Edit:
Around DNS (#12) - Advertising comes to .tel (#195) - Message List:

IMPORTANT: Telnic is still working on the TelProxy? update, so if you store a .tad record in a domain today, it will be displayed “as is” in the Text Header of the page. However, if you store your TAD in the _ad subfolder where the proxy is not looking, your record simply won't display. To store a record in that folder, set its owner correctly to owner="_ad". This way, you don't need to create a folder separately.

We will be keeping the community informed on further updates,
Telnic


Conclusion:

<typ:storeRecordRequest domainName=" mycompany.tel">
<typ:txt profiles="_all_" owner="_ad">
Etc.
.
.
<typ:text>desc</typ:text>
<typ:text>sample description</typ:text>
</typ:txt>
</typ:storeRecordRequest>


- It is still a mystery, but I am getting close...

Originally Posted by kprobe

Don't know where you get all this info, but you are totally incorrect. Every tel owner can place ads on their .tel domains, no ISP nor permission is needed. True you need SOAP API calls, but there are no restriction. I have created my own experimental interface for testing adverts and anyone is free to use it .... ????: NamePros.com http://www.namepros.com/showthread.php?t=561820 Quick update of your TEL domain header, free text keywords and affiliate advertisements Many people have already put ads in place with it. Enjoy. Mark

[plaggypig]

Social networking federation: why not use .tel?

[mactel]

Creating advertisement records for storing

1.) Preparation:

IN TXT ".tad" "1" "1" "51"
"Plumber"
"www.ReactFast.co.uk/Plumbers"
"uri" "http://www.reactfast.co.uk" "uri" "=243423543&z=42342343"
"desc" "24 Hour Fast Response Plumbers" "desc" "10% Book Online Discount
Today !"

And the advert settings, for stead.tel, for example, might look like this:

<typ:storeRecordRequest domainName=" stead.te">
<typ:txt profiles="_all_" owner="_ad">
<typ:text>.tad</typ:text>
<typ:text>1</typ:text>
<typ:text>1</typ:text>
<typ:text>51</typ:text>
<typ:text>Title of the ad</typ:text>
<typ:text>lable of the ad</typ:text>
<typ:text>uri</typ:text>
<typ:text>The new way to communicate</typ:text>
<typ:text>desc</typ:text>
<typ:text>sample description</typ:text>
</typ:txt>
</typ:storeRecordRequest>

2.) Final Version of Advertisment TXT records:

And the advert settings, for stead.tel, for example, might look like this:

<typ:storeRecordRequest domainName=" stead.tel">
<typ:txt profiles="_all_" owner="_ad">
<typ:text>.tad</typ:text>
<typ:text>1</typ:text>
<typ:text>1</typ:text>
<typ:text>51</typ:text>
<typ:text>Plumber</typ:text>
<typ:text>xwww.ReactFast.co.uk/Plumbers</typ:text>
<typ:text>xxxx://www.reactfast.co.uk=243423543&z=42342343</typ:text>
<typ:text></typ:text>
<typ:text>desc</typ:text>
<typ:text>24 Hour Fast Response Plumbers</typ:text>
<typ:text>desc</typ:text>
<typ:text>10% Book Online Discount Today !</typ:text>
</typ:txt>
</typ:storeRecordRequest>
.
.
The order for the syntax looks like this:


storeRecordRequest for Domain Name
Folder
Suffix
Position (Display Preference)
Location
Sort Sequence
Title
Label
Link
Text Content
Space
Text Content
Space
Text Content
storeRecordRequest


Result:

Which will create this advert, on top, on your TelProxy:

Plumber
24 Hour Fast Response Plumbers
10% Book Online Discount Today!
xwww.ReactFast.co.uk/Plumbers
.
.

[mactel]

To prevent "SOAP-ERROR", you should download the client.wsdl from your Telhosting provider,

Respectively:
To be able to advertise within your .tel, you need "internal SOAP API" form your .tel registrar.

Follow the instructions in the Telhosting_Client.php script:
With PHP, you MUST download the client.wsdl file from your provider, modify it a little bit, and then things will go fine. This information is contained at the top o the Telhosting_Client.php script.:

* 1.   Download the client WSDL from YOUR registrar, save it in the same directory as this file and name the downloaded file: client.wsdl
 *
 * 1.5  Don't know where your registrar put the WSDL file? Open an command-line client on UNIX and write:  dig _soap._nspapi.yourdomain.tel naptr where you replace yourdomain with your actual domain. Then take either the http or https url and append to it "?wsdl" (so it will end in "...client?wsdl")
 *      That's the url for your registrar's WSDL file.
 *
 * 2.   Edit client.wsdl -- find the string: "http://www.w3.org/2003/05/soap/bindings/HTTP/" and replace it by: "http://schemas.xmlsoap.org/soap/http". If you don't do that, PHP will throw a fatal error: "SOAP-ERROR: Parsing WSDL: PHP-SOAP doesn't support transport 'http://www.w3.org/2003/05/soap/bindings/HTTP/'".

There's a very good PHP DNS library that you should be using. It's called gDNS, and it can be found at phpclasses.org.

It's used very effectively in the .tel WordPress plugin:

(If if you PHP haven't SSL support, try to use:
telhosting.domainmonster.com/client?wsdl=1 , with the http:// infront.)

Excursion:

WSDL 1.0 (Sept. 2000) has been developed by IBM, Microsoft and Ariba to describe Web Services for their SOAP toolkit.

WSDL 1.1, published on March 2001, is the formalization of WSDL 1.0. No major changes were introduced between 1.0 and 1.1.

WSDL 1.2 (June 2003) is still a working draft at W3C. According to W3C: WSDL 1.2 is easier and more flexible for developers than the previous version. WSDL 1.2 attempts to remove non-interoperable features and also defined the better HTTP 1.1 binding. WSDL 1.2 was not supported by most of the SOAP servers/vendors.

WSDL 2.0 became a W3C recommendation on June 2007. WSDL 1.2 was renamed to WSDL 2.0 because it has substantial differences from WSDL 1.1. The changes are:

    * Adding further semantics to the description language
    * Removal of message constructs
    * No support for operator overloading
    * PortTypes renamed to interfaces
    * Ports renamed to endpoints.

There was some fit between WIDL and the XML-RPC system by UserLand. The former has since faded away, as message-based XML technologies have proven more popular than their procedural equivalents. The latter seems to be giving way to SOAP, which has support for message-oriented as well as procedural approaches.

SOAP describes envelope and message formats, and has a basic request/response handshake protocol. Additionally, Microsoft developed the SOAP Contract Language (SCL) earlier this year to provide a system for on-line service descriptions for SOAP-based applications. This work in SCL, in addition to other protocols and related work from IBM and Ariba, has pretty much been phased into WSDL.

Telnic Ltd. provides a Java-based TelHosting Software application. This application interacts with the DNS directly, and exposes a publicly available web service, using SOAP over HTTP as its protocol. Client applications implementing this SOAP interface can work with the TelHosting Software application to perform all .tel-related operations.

All APIs work by receiving request messages from the clients and sending response messages back to them unless the request message requires no response. All messages are expressed in XML, and their respective syntax is specified by an XML schema; see List of Schema Files. The messages must follow the specific format, see Message Format.
.

---------- Post added at 08:30 AM ---------- Previous post was at 07:28 AM ----------

.
Advertising records for advertising within .tel; "Request-response" principle:

WSDL Operation Types

The request-response type is the most common operation type.

Type:
Request-response

Definition:
The operation can receive a request and will return a response.

In the example above, the port "glossaryTerms" defines a request-response operation called "getTerm".

The "getTerm" operation requires an input message called "getTermRequest" with a parameter called "term", and will return an output message called "getTermResponse" with a parameter called "value".
.
WSDL bindings defines the message format and protocol details for a web service.

learn about SOAP and Web Services.

SOAP:

SOAP is a simple XML-based protocol that allows applications to exchange information over HTTP.

Or more simply: SOAP is a protocol for accessing a web service.

SOAP Tutorial:

SOAP HTTP Binding
This chapter is an introduction to the SOAP HTTP binding.

A SOAP method is an HTTP request/response that complies with the SOAP encoding rules.
HTTP + XML = SOAP
.
.
FINAL CONCLUSION FOR ADVERTISING WITHIN .TEL:

1.) You must use SOAP with 'storeRecord' for adding TXT ('.tad') with '_ad' as
owner.

2.) To be able to use SOAP: download the client.wsdl file from your provider, modify it a little bit.

3.) Save it in the same directory as the Telhosting_Client.php script, and name the downloaded file: client.wsdl.

4.) Edit client.wsdl, according to the Telhosting_Client.php script.
     If if your PHP hasn''t SSL support: try to use:
telhosting.domainmonster.com/client?wsdl=1 , with the http:// infront.

5.) Create Advertisement TXT records for your .tel domain, according to the following syntax:

Example Advert:
Plumber
24 Hour Fast Response Plumbers
10% Book Online Discount Today!
xwww.ReactFast.co.uk/Plumbers

Syntax:

<typ:storeRecordRequest domainName=" stead.tel">
<typ:txt profiles="_all_" owner="_ad">
<typ:text>.tad</typ:text>
<typ:text>1</typ:text>
<typ:text>1</typ:text>
<typ:text>51</typ:text>
<typ:text>Plumber</typ:text>
<typ:text>xwww.ReactFast.co.uk/Plumbers</typ:text>
<typ:text>xxxx://www.reactfast.co.uk=243423543&z=42342343</typ:text>
<typ:text></typ:text>
<typ:text>desc</typ:text>
<typ:text>24 Hour Fast Response Plumbers</typ:text>
<typ:text>desc</typ:text>
<typ:text>10% Book Online Discount Today !</typ:text>
</typ:txt>
</typ:storeRecordRequest>

Scheme:

storeRecordRequest for Domain Name
Folder
Suffix
Position (Display Preference)
Location
Sort Sequence
Title
.
.
Etc.

.
Good luck!:
Please send a feedback, about your achievements with advertising within your .tel domain.
Thank you, for your patience, and staying power, etc.

Your 

MacTel :wave:
.
P.S.:
To find the correct end-point for your .tel domain, use 

DIG/nslookup commands and query _soap._nspapi.yourTelDomain.tel. 

The returned records should point to the addresses of the endpoint, such as MyTelProvider:80/client

For more questions on SOAP, please consult our newly updated FAQ materials. 
.
There is also a SOAP forum at the Telnic website.
.
Each registrar has its own Telhosting platform, and therefore its own SOAP API entrypoint. You can find the SOAP entrypoints in http and https for your domain by simply querying the NAPTR records for:

_soap._nspapi.[YOUR-DOMAIN].tel

This is called "autoprovisioning", and you can use it to automagically find the right SOAP API entrypoints. Similarly, you can find the web interface (and therefore JSON) entrypoints with:

_web._nspapi.[YOUR-DOMAIN].tel

Please use your correct API url, it should work. 

Here's an example in PHP of how to find a domain's SOAP API entrypoint, otherwise called "autoprovisioning":

<?php
$dom = 'MYDOMAIN.tel';
$pattern = "/(https:.+)!\" \.$/m";
$dig = shell_exec("dig @208.67.222.222 _soap._nspapi.${dom} naptr");
if (preg_match($pattern, $dig, $regs)) {
    echo "The https URL for the SOAP API is: {$regs[1]}\n";
};
?>

.
Quote from Pierre:

"I confirm using the good WSDL will definitely help!

You have to be carefull with the WSDL. The PHP SOAP implementation is bugged, and it won't validate the transport binding URL (differences between SOAP 1.1 and SOAP 1.2). A bug report has been filled so you can expect it to be resolved in the next stable version of PHP. By the meantime, there is fortunately a workaround:

1. Download the client WSDL from your registrar, save it in the same directory than the TelHosting? class and name the downloaded file: client.wsdl.

2. Edit client.wsdl -- find the string: "http://www.w3.org/2003/05/soap/bindings/HTTP/" and replace it by: "http://schemas.xmlsoap.org/soap/http". If you don't do that, PHP will throw a fatal error: "SOAP-ERROR: Parsing WSDL: PHP-SOAP doesn't support transport 'http://www.w3.org/2003/05/soap/bindings/HTTP/'".

3. Edit the TelHosting? class -- look for: $config['wsdl'] (around line 173) and set the variable to: "./client.wsdl" instead of the full URL. PHP SOAP implementation uses fopen() to get the WSDL so you can specify a local file instead of an URL.

4. Retry, it should work! "
.
Sample PHP code at:
dev.telnic.org/trac/browser/apps/php/trunk 

Update of the sample PHP code to support automatic de-duplication of keywords. Automatic de-duplication is on by default. You can turn it off by writing:

$client->set_search_data($domain, $keywords->searchData, FALSE);
.
BTW:
1993, 16 years ago, a IT speciallist commented:
"It would be useful to take advantage of the widespread use and scaleability of the DNS to store information that has not been previously defined."
Seven years later, ca. 2000, a company named "Telnic", picked up the idea, to create "dot tel".
Mind you: dot tel could of been create 20 years ago. Or 15, or 10 years ago. Anyway: It is here, now. Probably the best time, as people are crazy after iPhones, and nearly every kidd has a iPhone. Just whait and see...
.
.

Quote Henry:
????: NamePros.com http://www.namepros.com/showthread.php?t=561820
????: NamePros.com http://www.namepros.com/showthread.php?t=561820
"One last point: the TelHosting control panel won't support ad management, that's not its purpose. I inserted the ad above using the APIs, but I suspect that ad providers will be doing something even simpler by providing an ad DNS server."

Personal comment:
Henry, I do not agree with you in the slightest.
The TelHosting control panel should indeed support ad management.
Yes, oh yes, oh yes...
Users want to post their adverts in a easier way.
But, ok: Once they set up their internal SOAP API, and they now about the syntax rules, storing the advertisment records, should be quit easy, then.

But I guess, many users would be put off, by the complecated SOAP API stuff.
Give them something, that works aout of the box, and is easy to control, and to handle.

You can say, this, and that, Henry, but if it won't be good for business, it won't be good for business, and that is that.
You got to decide, if you want to be restrictive, because it is the concept, that has to be so, or if you want to give in, and adapt to what the community of .tel domain owners and users would like to use.
.
It is not cool, to have "Advertising within .tel" announced, by the world press, and then only a few developers, who have been struggling since five months, and finally grasped the proceeding, are capable of putting ads on the TelProxy. Only showing off with their achievments, but not wanting to help others, to troubleshoot.

It is another desaster, just like the "Contact Us" page (integrating .tel in your existing website), which is not applyable as intended by Telnic, because the LOC records are not working.

It is better to announce something that works 100%, than announce half developed things.

It is the sad truth, Henry, and it is your responsibility, to make things better in future.

We can't have a disaster every time, "average .tel user" wants to improve his .tel domain.
.

Edit:

kprobe's tool at mytel.me, is fine, but not all users want to only depend on the tool at mytel.me, even if it is a good tool: Users might want to be able to manage their advertisments by coding their TXT records, etc, by their own.

(An advertisment is a TXT record with the '.tad' prefix, placed in the '_ad sub-domain' of the current domain, such as '_ad.mybusiness.tel'.

The syntax of the ad record, is specified by an XML schema.

To be able to advertise within your .tel, you need "internal SOAP API" from your .tel registrar / provider:
SOAP is a simple XML-based protocol that allows applications to exchange information over HTTP.
HTTP + XML = SOAP
Or more simply: SOAP is a protocol for accessing a web service.

To be able to advertise within your .tel, you need the client.wsdl file from your .tel registrar / provider:
WSDL bindings defines the message format and protocol details for a web service.

To store a ad record in the '_ad' folder, set its owner within the syntax of the ad record correctly to owner="_ad". This way, you don't need to create a folder separately:

<typ:storeRecordRequest domainName="mybusiness.tel">
<typ:txt profiles="_all_" owner="_ad">

But: the TelHosting control panel won't support ad management. You have to inserted your ad by using the APIs,

Telnic Ltd. provides a Java-based TelHosting Software application. This application interacts with the DNS directly, and exposes a publicly available web service, using SOAP over HTTP as its protocol. Client applications implementing this SOAP interface can work with the TelHosting Software application to perform all .tel-related operations.

In addition to the client service API, the TelHosting Software exposes an internal API for administration purposes.

To be able to advertise within your .tel, you need "internal SOAP API", as well as client.wsdl file from your .tel registrar / provider, and then modify the file a little bit:

Find the string: "http://www.w3.org/2003/05/soap/bindings/HTTP/" and replace it by: "http://schemas.xmlsoap.org/soap/http".

Edit the TelHosting class: look for: $config['wsdl'] (around line 173) and set the variable to: "./client.wsdl" instead of the full URL.

And now, you can insert your ad records by using the APIs.

And your advertisement should show up, on your TelProxy.)
.
It may be complecated, but that is how it is:
Currently, you can choose between doing it your self, or going to mytel.me. and use the tool, which is offered to use, and which is free.

The guys from Jepaa, will soon come up with a solution, which you will be able to find within TEL-MACHINE,

Have fun!
.

[plaggypig]

Google: We Don’t Use Keywords Meta Tag - validates my points from the earlier discussion in this thread re: META tags and SEO.

[mactel]

.
Thank you, plaggypig,
and heartily greetings.

[hasseily]

mactel: you do not need any "special" "internal" API to store ads in .tel domains. Inserting ads can be done on any domain. It's just a specially formatted TXT record.
Furthermore:

Quote:

The TelHosting control panel should indeed support ad management.

The TelHosting control panel is not the end-all-be-all of management of a .tel. It's something for the average user/company to work with. There are many developers out there who are building specialized tools for different types of users, such as those building directories, or those wanting to manage ads, etc...
????: NamePros.com http://www.namepros.com/showthread.php?t=561820
Having the Community TelHosting software be the final say in .tel domain management is not what we're aiming for, as we are certain that there is absolutely no way to accommodate all different .tel owner types. That's why you have standardized APIs and you will have a TelHosting accreditation system for anyone to roll out their own.

Below is sample PHP code to enter an ad:

PHP Code:

<?php
include('Telhosting_Client.php');
$ad = array(
????: NamePros.com http://www.namepros.com/showthread.php?t=561820
    'text' => array('.tad', '1',
                    '100', '95',
                    'Advert Title', 'Click here!',
                    'uri', 'http://www.telnic.org',
                    'uri', '?params=some+params', 
                    'desc', "This is a sample ad\nLine 2 of",
                    'desc', " the ad, whose description can be very long"),
    'profiles' => '_all_',
    'owner' => '_ad'
);
// Config
// NOTE: THIS USES A LOCAL client.wsdl FILE AS EXPLAINED IN THE Telhosting_Client.php DOCS
$config = array();
$config['login'] = 'INSERT_USERNAME_HERE';
$config['password'] = 'INSERT_PASSWORD_HERE';
$config['wsdl'] = './client.wsdl';
$domain = 'my.domain.tel';

// Initialize our client
$client = new Telhosting_client($config);
// Insert some data
$client->store_record($domain, 'txt', $ad);
?>

Download Telhosting_Client.php from the Telnic developer site.

H