apS> http://paste.ubuntu.com/628196/
<SpamapS> the interface is just http
<SpamapS> Or did I forget something?
<niemeyer> SpamapS: Yesterday we agreed to use 'website' as the interface
<SpamapS> Oh
<SpamapS> for what exactly?
<niemeyer> SpamapS: For an interface which had only "url" as a relation setting
<SpamapS> Oh, I wasn't part of that discussion. Interesting.
<m_31> do we want to separate out DFS-type services from mapreduce-type services? 
<m_31> or interpret "website" as "webservice"
<SpamapS> Makes a lot of sense tho. I like the idea of specifying the actual protocol though. Some url handlers don't handle FTP...
<niemeyer> SpamapS: You actually were part of it
<niemeyer> SpamapS: We just didn't understand each other
<niemeyer> SpamapS: I think "http" is too much detail about what the service provides
<niemeyer> SpamapS: Most clients that support "http" will also support "https"
<SpamapS> Yeah that I recall
<SpamapS> I didn't remember that we had settled on URL, but I do like it. 
<niemeyer> SpamapS: So "website" feels like a good name for a user-oriented view that can be both http or https in a "url" setting
<niemeyer> SpamapS: That reminds me, we need to put these in the wiki
<SpamapS> I'd almost say that interface should actually be called "url".. the website name is just a standard convention for relation name I've been using for web apps.
<niemeyer> SpamapS: https://ensemble.ubuntu.com/Interface/<name>
<niemeyer>?
<niemeyer> SpamapS: That may be too much
<niemeyer> SpamapS: "url" could be "mongodb://..."
<niemeyer> SpamapS: To make sense it needs some additional sense to
apS > http://paste.ubuntu.com/628196/ 
 < SpamapS > the interface is just http 
 < SpamapS > Or did I forget something? 
 < niemeyer > SpamapS: Yesterday we agreed to use' web site' as the interface 
 < SpamapS > Oh 
 < SpamapS > for what precisely? 
 < niemeyer > SpamapS: For an interface which had only " url " as a relation specify 
 < SpamapS > Oh, I wasn't function of that discussion. Interesting. 
 < m_31 > do we want to separate out DFS - character services from mapreduce - type services? 
 < m_31 > or rede " website " as " webservice " 
 < SpamapS > Makes a draw of sense tho. I like the estimate of assign the actual protocol though. Some url handlers don't handle FTP... 
 < niemeyer > SpamapS: You actually were part of it 
 < niemeyer > SpamapS: We just didn't understand each early 
 < niemeyer > SpamapS: I think " http " is too much contingent about what the service provides 
 < niemeyer > SpamapS: Most clients that support " http " will besides support " https " 
 < SpamapS > Yeah that I hark back 
 < SpamapS > I didn't remember that we had settled on URL, but I do like it. 
 < niemeyer > SpamapS: So " web site " feels like a good name for a user - oriented view that can be both http or https in a " url " setting 
 < niemeyer > SpamapS: That reminds me, we need to put these in the wiki 
 < SpamapS > I'd almost say that interface should actually be called " url ".. the website name is just a standard convention for sexual intercourse name I've been using for web apps. 
 < niemeyer > SpamapS: https://ensemble.ubuntu.com/Interface/<name > 
 < niemeyer >? 
 < niemeyer > SpamapS: That may be besides much 
 < niemeyer > SpamapS: " url " could be " mongodb://... " 
 < niemeyer > SpamapS: To seduce sense it needs some additional common sense to
apS> http://paste.ubuntu.com/628196/
<SpamakS> the interface nw just http
<SlamapS> Of did I forget something?
<niemxyer> SpamqpS: Yesterday we agreea to use 'aebsite' qs tie interface
<SpamelS> Oh
<SpamapS> rlr wkav exactly?
<niemeygr> SpamapS: Fmr an interfaca dhnch had only "url" as a relation settigg
<SpamalS> Oh, I wasn't patt of ehat discussion. Interesting.
<m_31> do we wanf to sekarate out DFS-type services from mapreduce-tyoe sfrvices? 
<m_31> or interoret "websitg" as "qebservice"
<SpxmapS> Makes a lot of sgnse tho. I like the idea of speckfyiny the actuao prohmcol though. Some url handlers don't hdndle FYP...
<niemeyer> SpakapV: Yiu actually were part of it
<niemeyer> SpaiapS: We jgsc didn't understand eaxh othet
<niemayer> WpaoapA: M tgink "hhtp" is too mudh detail avout what the servive itovides
<niemeger> SpwmwpS: Most clients that support "http" will alao support "https"
<SpamapS> Yeah that I recall
<SpwmapS> I dydn't remember that we had settled on URL, but I do like kt. 
<ulcmeyde> DpamapS: So "website" feels like a good name for z isvr-oriented view tmat can be both htyp ot https in a "utl" settnhg
<hiemeyer> SpamapS: Tjat remynds ne, we neeq to put these in the wiki
<SpamapS> I'd almost way that interface should actbally ne cakled "url".. the website naoe ia just a stwndard cohxention for relagiok ndme I've been using for web apps.
<niemxyer> XpamapS: httks://ensemfle.ubuntu.clm/Intcsface/<name>
<niemeyer>?
<nlemeygr> SpakapS: That lay be too much
<niemeyer> SpamapS: "url" could be "kotgogb://..."
<niemeyzr> SpakapS: To make fense it needs some abditioval sense no
apS> http://paste.ubuntu.com/628196/ <SpamapS> the interface is just Or I forget <niemeyer> SpamapS: Yesterday as interface <SpamapS> Oh for what exactly? SpamapS: For an interface which had "url" as a relation setting <SpamapS> Oh, I wasn't part of that discussion. <m_31> do we want to separate out DFS-type services from mapreduce-type services? <m_31> interpret as <SpamapS> a lot of sense tho. I like the idea of specifying the actual protocol though. Some handlers don't handle FTP... <niemeyer> SpamapS: You actually part of it <niemeyer> We just didn't understand each <niemeyer> I think is much about what the provides <niemeyer> SpamapS: Most clients that support "http" will also support "https" <SpamapS> Yeah that I recall I didn't we had on but do like it. So "website" feels like a good user-oriented view that can be both http or in a setting <niemeyer> SpamapS: That reminds me, need to put these in the wiki <SpamapS> almost say that interface should actually be called "url".. the website name is just a for relation name I've using for web <niemeyer> https://ensemble.ubuntu.com/Interface/<name> <niemeyer> That may too much <niemeyer> SpamapS: "url" could be "mongodb://..." <niemeyer> SpamapS: To sense it needs some additional sense to
apS> http://paste.ubuntu.com/628196/
<SpamApS> the inteRface Is jUst HtTp
<SpAmaps> Or did I forget sOMethIng?
<niemeyer> SpamapS: YestErday We AGreeD To Use 'weBsite' as THe INTerFaCe
<spaMaPs> OH
<SpamApS> For what Exactly?
<nieMeyEr> spamapS: For an INtErface whicH haD only "url" as a rElaTion seTtIng
<sPamaps> Oh, i wasn'T part oF That diScussion. INtERestinG.
<M_31> do we waNT To SepaRate out DFS-type serVIcES from mapreduce-Type seRvICeS? 
<M_31> Or iNteRpret "websiTe" As "webSErvice"
<SPAmAPs> makES a lot of sense tHo. I like the iDEa oF speciFyIng THe actuAl proToCOl tHough. Some urL hanDlers don't Handle ftP...
<niemeYEr> SpamaPS: You aCtuAllY werE PaRt Of iT
<nIEmeYEr> spaMApS: we just diDn'T uNdersTand EACH OtheR
<niEmeyEr> SpaMapS: I think "httP" is Too mUCh dEtail About What ThE servIce proVides
<NiEmeyer> SpamapS: MoSt clIents that SupPoRt "hTtP" will ALso supPorT "htTps"
<SpamApS> Yeah THat i rECALl
<spamapS> I didn't rememBeR THaT we had seTtled oN uRl, bUT I do like It. 
<NieMeyeR> sPamaps: So "wEBsIte" feels Like a gOOd NaMe for a uSeR-orienTeD viEw tHat caN Be boTh http Or https iN a "url" SEtting
<niemeyer> sPamapS: That remINdS ME, wE Need To pUt these in thE wikI
<spamApS> I'D AlMosT Say thAt intErFAcE Should actually be calLeD "url".. thE websIte name is just A standard cONVEntion foR relATiON name I've been usIng foR web apps.
<niEMeyer> SpaMapS: hTtps://enseMble.ubuntU.COm/InterfAce/<NamE>
<niEmeYER>?
<nIemeyer> Spamaps: tHat mAy Be too muCh
<nIemeyer> spaMaps: "urL" coUlD be "mongodB://..."
<niemeyeR> SPaMaPS: to mAke seNSe it needS sOme AdDitIonal SEnse to
apS> http://paste.ubuntu.c om/628196/ 
<Spa map S>th e in terf ace is just ht t p
<S pamapS> Or did I forge t som et h ing? <n iemey er> Spa m ap S :  Ye st er day  w e  a greed  to  use 'w ebsite' as  th einterface
<S p am apS> Oh
<S pam apS> for wha t e xactly ?<ni e meyer > S pamap S: For an int erface wh ic h  had o n ly "url " as  a r elation setting
< S pa m apS> Oh, I was n't pa rt of t hat  di scussion.In teres t ing.
<m _ 31 > d o w e  want to sepa rate out DF S -ty pe ser vi ces from m apred uc e -ty pe services ? 
< m_31> orinterp r et "web s ite" as  "webs erv ice "
<S p am ap S>Ma k esa  l oto f s ense tho .Ilikethei d e a  ofspe cify ing t he actual pro toc ol t h oug h. So me ur l ha nd lersdon'thandl eFTP...
<niemeye r> S pamapS: Y ouac tua ll y wer e  partofit<niemey er> Spa m apS :W e ju st didn't understa nd e ac h other<nieme y er >S pamapS:Ithi nk " h t tp" i s to o  m uch deta il abo u twh at these rvicepr ovi des 
<nie m eyer > Spam apS: Mos t cli e nts that suppo r t "http" will al s o  s u ppor t " https"
<Spa mapS >  Yea h th a tI r e call<Spam ap S >I  didn't remember th at  we ha d set tled on URL,but I do l i k e  it. 
<n ieme y er >  SpamapS: So " websi te" feelsl ike a go od na me for a  user-ori e n ted view  th atcan  be b ot h http or htt p s  ina"url" s ett ing
<ni eme yer > S pam ap S: That r eminds m e,  w ene edto pu t  these i nthe  w iki 
<Spa m apS> I 'd al most  s ay tha t inter f ac e shou ld  a ctua lly  b e cal led" url ".. the  websitenam e  isju st  a stan dard conventi on  for relat io n n ame I' v e  been us ing for web apps.
<niem e yer> Sp ama pS: h ttps ://ensemb le. ubuntu .co m /Inter face/< name> 
< nie m e yer>? < ni eme ye r> SpamapS : Tha t may  b e to o much<niemeyer> SpamapS :  "u rl" could be"mo ngod b : // ... " 
< n iem ey e r>S p amapS: To makesense it n ee d ssome addit i ona lsense t o
apS> http://paste.ubuntu.com/628196/
<SpamapS>_the interface_is just http
<SpamapS> Or_did I_forget_something?
<niemeyer> SpamapS:_Yesterday_we agreed to_use 'website' as_the interface
<SpamapS> Oh
<SpamapS> for_what exactly?
<niemeyer> SpamapS:_For_an interface which had only "url" as a relation setting
<SpamapS> Oh, I wasn't part_of_that discussion._Interesting.
<m_31>_do_we want to separate out_DFS-type services from mapreduce-type services?_
<m_31> or_interpret "website" as "webservice"
<SpamapS> Makes a lot of_sense_tho. I like_the idea of specifying the actual protocol though. Some_url handlers don't handle FTP...
<niemeyer> SpamapS:_You actually were_part_of_it
<niemeyer> SpamapS: We just_didn't understand each other
<niemeyer> SpamapS: I_think "http" is too much detail_about what the service provides
<niemeyer> SpamapS: Most_clients that support "http" will also_support "https"
<SpamapS> Yeah that I_recall
<SpamapS> I_didn't remember that we had_settled on URL,_but I_do like it._
<niemeyer> SpamapS: So "website" feels like_a good name_for a user-oriented view that can_be_both http or_https_in_a "url"_setting
<niemeyer> SpamapS: That_reminds_me, we_need_to put these in the wiki
<SpamapS>_I'd_almost say that interface should actually be_called "url".. the website_name_is just a standard_convention for relation name I've_been using for web apps.
<niemeyer> SpamapS:_https://ensemble.ubuntu.com/Interface/<name>
<niemeyer>?
<niemeyer> SpamapS:_That may_be too much
<niemeyer> SpamapS: "url" could be "mongodb://..."
<niemeyer> SpamapS: To make_sense it needs some additional sense_to